CVE-2026-81859

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-09-04. a secondary CVSS source baseline 6.2; sources differ by 0.0.

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

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

CP4BA - IBM Enterprise Records could allow a local attacker to obtain sensitive information due to the use of a broken or risky cryptographic algorithm.

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

Published

September 4, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
Patch available.
generic Patch Available

Security Bulletin: Multiple security vulnerabilities are addressed with IBM Cloud Pak for Business Automation iFixes for August 2026.

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

Vendor Advisories for CVE-2026-81859(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 16× in last 7d / 42× 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 21:39 UTCGHSA enrichment
  2. 2026-09-18 21:22 UTCEG score recompute
  3. 2026-09-18 21:22 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-17 20:23 UTCEG score recompute
  6. 2026-09-17 20:23 UTCGHSA enrichment
  7. 2026-09-16 18:28 UTCEG score recompute
  8. 2026-09-16 18:28 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-15 17:15 UTCEG score recompute
  11. 2026-09-15 17:15 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 16:58 UTCEG score recompute
  15. 2026-09-14 16:58 UTCGHSA enrichment
  16. 2026-09-13 16:42 UTCGHSA enrichment
  17. 2026-09-12 16:25 UTCEG score recompute
  18. 2026-09-12 16:25 UTCGHSA enrichment
  19. 2026-09-11 16:08 UTCEG score recompute
  20. 2026-09-11 16:08 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 15:49 UTCEG score recompute
  24. 2026-09-10 15:49 UTCGHSA enrichment
  25. 2026-09-09 15:32 UTCEG score recompute
Show 17 more
  1. 2026-09-09 15:32 UTCGHSA enrichment
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 15:15 UTCGHSA enrichment
  4. 2026-09-07 20:10 UTCGHSA enrichment
  5. 2026-09-06 19:53 UTCEG score recompute
  6. 2026-09-06 19:53 UTCGHSA enrichment
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-05 19:35 UTCEG score recompute
  9. 2026-09-05 19:35 UTCGHSA enrichment
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-04 19:19 UTCEG score recompute
  12. 2026-09-04 19:19 UTCGHSA enrichment
  13. 2026-09-04 18:40 UTCEG score recompute
  14. 2026-09-04 18:40 UTCGHSA enrichment
  15. 2026-09-04 15:21 UTCEG score recompute
  16. 2026-09-04 15:09 UTCEG score recompute
  17. 2026-09-04 15:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81859?
CVE-2026-81859 is a medium vulnerability published on September 4, 2026. CP4BA - IBM Enterprise Records could allow a local attacker to obtain sensitive information due to the use of a broken or risky cryptographic algorithm.
When was CVE-2026-81859 disclosed?
CVE-2026-81859 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81859 actively exploited?
CVE-2026-81859 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 98.6% of all scored CVEs.
What is the CVSS score of CVE-2026-81859?
CVE-2026-81859 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-81859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81859, 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-2026-81859

Explore →

Is Your Infrastructure Affected by CVE-2026-81859?

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

Start Free Scan →Browse All CVEs