CVE-2025-36253

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

February 2, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
Patch available.
generic Patch Available

Security Bulletin: Multiple Vulnerabilities in IBM Concert Software.

https://www.ibm.com/support/pages/node/7257565

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:29 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-10 09:33 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-04 05:05 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:38 UTCEPSS rescore
  17. 2026-09-01 00:04 UTCOSV refresh
  18. 2026-08-30 19:16 UTCEPSS rescore
  19. 2026-08-30 01:21 UTCEPSS rescore
  20. 2026-08-28 21:40 UTCEPSS rescore
  21. 2026-08-27 14:24 UTCEPSS rescore
  22. 2026-08-26 14:45 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:54 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:47 UTCEPSS rescore
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-15 01:29 UTCEPSS rescore
  9. 2026-08-15 00:42 UTCGHSA enrichment
  10. 2026-08-14 11:40 UTCEG score recompute
  11. 2026-08-14 11:40 UTCGHSA enrichment
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 03:50 UTCEG score recompute
  14. 2026-08-13 03:50 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-10 10:03 UTCGHSA enrichment
  17. 2026-08-09 16:10 UTCEG score recompute
  18. 2026-08-09 16:10 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-08 16:36 UTCEPSS rescore
  21. 2026-08-07 23:01 UTCEG score recompute
  22. 2026-08-07 23:01 UTCGHSA enrichment
  23. 2026-08-07 16:26 UTCEPSS rescore
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 04:33 UTCEG score recompute
  26. 2026-08-06 04:33 UTCGHSA enrichment
  27. 2026-08-04 15:09 UTCEPSS rescore
  28. 2026-08-04 10:37 UTCEPSS rescore
  29. 2026-08-03 10:35 UTCEPSS rescore
  30. 2026-08-02 21:41 UTCEG score recompute▲ 1.60
  31. 2026-08-02 21:41 UTCGHSA enrichment
  32. 2026-08-02 02:26 UTCEPSS rescore
  33. 2026-08-01 04:15 UTCEPSS rescore
  34. 2026-07-31 01:21 UTCOSV refresh
  35. 2026-07-30 16:27 UTCEPSS rescore
  36. 2026-07-30 01:29 UTCEPSS rescore
  37. 2026-07-28 15:35 UTCEPSS rescore
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-25 14:17 UTCEPSS rescore
  40. 2026-07-25 14:17 UTCEPSS rescore
  41. 2026-07-24 14:17 UTCEPSS rescore
  42. 2026-07-23 02:54 UTCEG score recompute
  43. 2026-07-22 14:07 UTCEPSS rescore
  44. 2026-07-22 14:07 UTCEPSS rescore
  45. 2026-07-21 15:24 UTCEPSS rescore
  46. 2026-07-20 17:07 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-19 14:30 UTCEPSS rescore
  49. 2026-07-19 02:28 UTCEPSS rescore
  50. 2026-07-19 02:28 UTCEPSS rescore
  51. 2026-07-18 10:04 UTCEPSS rescore
  52. 2026-07-18 10:04 UTCEPSS rescore
  53. 2026-07-16 17:02 UTCEPSS rescore
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 01:59 UTCEPSS rescore
  57. 2026-07-15 01:59 UTCEPSS rescore
  58. 2026-07-13 22:29 UTCEPSS rescore
  59. 2026-07-13 22:29 UTCEPSS rescore
  60. 2026-07-13 09:38 UTCOSV refresh
  61. 2026-07-13 06:12 UTCEPSS rescore
  62. 2026-07-12 05:46 UTCEPSS rescore
  63. 2026-07-11 08:27 UTCEPSS rescore
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-09 19:09 UTCEPSS rescore
  66. 2026-07-09 19:09 UTCEPSS rescore
  67. 2026-07-07 13:45 UTCEPSS rescore
  68. 2026-07-06 16:27 UTCEPSS rescore
  69. 2026-07-06 16:27 UTCEPSS rescore
  70. 2026-07-06 02:23 UTCEPSS rescore
  71. 2026-07-05 02:30 UTCEPSS rescore
  72. 2026-07-04 06:30 UTCEPSS rescore
  73. 2026-07-01 15:06 UTCEPSS rescore
  74. 2026-07-01 15:06 UTCEPSS rescore
  75. 2026-06-30 23:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-36253?
CVE-2025-36253 is a high vulnerability published on February 2, 2026. IBM Concert 1.0.0 through 2.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
When was CVE-2025-36253 disclosed?
CVE-2025-36253 was first published in the National Vulnerability Database on February 2, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36253 actively exploited?
CVE-2025-36253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.3% of all scored CVEs.
What is the CVSS score of CVE-2025-36253?
CVE-2025-36253 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-36253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36253, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-36253

Explore →

Is Your Infrastructure Affected by CVE-2025-36253?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs