CVE-2025-36271

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-29. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

IBM Integrated Analytics System 1.0.0.0 through 1.0.31.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 2, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM Integrated Analytics System (IIAS) is affected by a predictable salt vulnerability in Magneto component

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

Vendor Advisories for CVE-2025-36271(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 62× 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.

  1. 2026-09-19 06:13 UTCEG score recompute
  2. 2026-09-19 06:13 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 05:39 UTCEG score recompute
  5. 2026-09-18 05:39 UTCGHSA enrichment
  6. 2026-09-17 19:29 UTCEPSS rescore
  7. 2026-09-17 05:06 UTCEG score recompute
  8. 2026-09-17 05:06 UTCGHSA enrichment
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-16 05:14 UTCEPSS rescore
  11. 2026-09-16 04:32 UTCGHSA enrichment
  12. 2026-09-15 03:48 UTCEG score recompute
  13. 2026-09-15 03:48 UTCGHSA enrichment
  14. 2026-09-14 03:14 UTCEG score recompute
  15. 2026-09-14 03:14 UTCGHSA enrichment
  16. 2026-09-13 16:46 UTCEPSS rescore
  17. 2026-09-13 02:41 UTCEG score recompute
  18. 2026-09-13 02:41 UTCGHSA enrichment
  19. 2026-09-12 15:00 UTCEPSS rescore
  20. 2026-09-12 02:07 UTCEG score recompute
  21. 2026-09-12 02:07 UTCGHSA enrichment
  22. 2026-09-11 14:52 UTCEPSS rescore
  23. 2026-09-11 09:35 UTCEPSS rescore
  24. 2026-09-11 01:33 UTCEG score recompute
  25. 2026-09-11 01:33 UTCGHSA enrichment
Show 37 more
  1. 2026-09-10 09:33 UTCEPSS rescore
  2. 2026-09-10 00:59 UTCGHSA enrichment
  3. 2026-09-09 00:26 UTCEG score recompute
  4. 2026-09-09 00:26 UTCGHSA enrichment
  5. 2026-09-08 21:59 UTCEPSS rescore
  6. 2026-09-07 17:24 UTCEG score recompute
  7. 2026-09-07 17:24 UTCGHSA enrichment
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-06 16:51 UTCEG score recompute
  10. 2026-09-06 16:51 UTCGHSA enrichment
  11. 2026-09-06 13:46 UTCEPSS rescore
  12. 2026-09-05 16:17 UTCEG score recompute
  13. 2026-09-05 16:17 UTCGHSA enrichment
  14. 2026-09-04 15:43 UTCEG score recompute
  15. 2026-09-04 15:43 UTCGHSA enrichment
  16. 2026-09-04 05:05 UTCEPSS rescore
  17. 2026-09-03 15:09 UTCGHSA enrichment
  18. 2026-09-02 14:34 UTCEG score recompute
  19. 2026-09-02 14:34 UTCGHSA enrichment
  20. 2026-09-02 14:11 UTCEPSS rescore
  21. 2026-09-01 20:07 UTCEG score recompute
  22. 2026-09-01 20:07 UTCGHSA enrichment
  23. 2026-09-01 13:53 UTCEPSS rescore
  24. 2026-09-01 04:38 UTCEPSS rescore
  25. 2026-08-31 19:30 UTCEG score recompute
  26. 2026-08-31 19:30 UTCGHSA enrichment
  27. 2026-08-31 18:56 UTCEG score recompute
  28. 2026-08-31 18:56 UTCGHSA enrichment
  29. 2026-08-30 23:49 UTCEG score recompute
  30. 2026-08-30 23:49 UTCGHSA enrichment
  31. 2026-08-30 19:16 UTCEPSS rescore
  32. 2026-08-30 01:21 UTCEPSS rescore
  33. 2026-08-29 23:15 UTCEG score recompute
  34. 2026-08-29 23:15 UTCGHSA enrichment
  35. 2026-08-28 22:41 UTCEG score recompute
  36. 2026-08-28 22:01 UTCEG score recompute
  37. 2026-08-28 21:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-36271?
CVE-2025-36271 is a medium vulnerability published on August 28, 2026. IBM Integrated Analytics System 1.0.0.0 through 1.0.31.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
When was CVE-2025-36271 disclosed?
CVE-2025-36271 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36271 actively exploited?
CVE-2025-36271 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 94.2% of all scored CVEs.
What is the CVSS score of CVE-2025-36271?
CVE-2025-36271 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-36271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36271, 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-36271

Explore →

Is Your Infrastructure Affected by CVE-2025-36271?

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