CVE-2026-10534

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

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

IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to buffer overflow in the IXF IMPORT parser.

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

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (1)

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

Security Bulletin: IBM® Db2® is vulnerable to buffer overflow in the IXF IMPORT parser (CVE-2026-10534)

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

Vendor Advisories for CVE-2026-10534(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 43× in last 7d / 48× 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-08-20 09:40 UTCGHSA enrichment
  2. 2026-08-20 05:26 UTCGHSA enrichment
  3. 2026-08-20 01:11 UTCGHSA enrichment
  4. 2026-08-19 20:57 UTCEG score recompute
  5. 2026-08-19 20:57 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 16:41 UTCGHSA enrichment
  8. 2026-08-19 12:24 UTCGHSA enrichment
  9. 2026-08-19 08:08 UTCGHSA enrichment
  10. 2026-08-19 03:54 UTCGHSA enrichment
  11. 2026-08-18 23:40 UTCGHSA enrichment
  12. 2026-08-18 19:27 UTCGHSA enrichment
  13. 2026-08-18 15:13 UTCEG score recompute
  14. 2026-08-18 15:13 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 10:33 UTCGHSA enrichment
  17. 2026-08-18 06:18 UTCGHSA enrichment
  18. 2026-08-18 02:03 UTCGHSA enrichment
  19. 2026-08-17 21:46 UTCGHSA enrichment
  20. 2026-08-17 17:28 UTCEG score recompute 1.40
  21. 2026-08-17 17:28 UTCGHSA enrichment
  22. 2026-08-17 17:24 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  23. 2026-08-17 11:44 UTCGHSA enrichment
  24. 2026-08-17 00:52 UTCEG score recompute
  25. 2026-08-17 00:52 UTCGHSA enrichment
Show 23 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:02 UTCGHSA enrichment
  3. 2026-08-16 03:12 UTCEG score recompute
  4. 2026-08-16 03:12 UTCGHSA enrichment
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 16:22 UTCGHSA enrichment
  7. 2026-08-15 05:32 UTCEG score recompute
  8. 2026-08-15 05:32 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 18:41 UTCGHSA enrichment
  11. 2026-08-14 07:51 UTCEG score recompute
  12. 2026-08-14 07:51 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 21:01 UTCGHSA enrichment
  15. 2026-08-13 14:24 UTCEG score recompute
  16. 2026-08-13 14:24 UTCGHSA enrichment
  17. 2026-08-13 13:56 UTCEG score recompute
  18. 2026-08-13 13:56 UTCGHSA enrichment
  19. 2026-08-13 09:10 UTCEG score recompute
  20. 2026-08-13 09:10 UTCGHSA enrichment
  21. 2026-08-12 22:21 UTCEG score recompute
  22. 2026-08-12 21:41 UTCEG score recompute
  23. 2026-08-12 21:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-10534?
CVE-2026-10534 is a critical vulnerability published on August 12, 2026. IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to buffer overflow in the IXF IMPORT parser.
When was CVE-2026-10534 disclosed?
CVE-2026-10534 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10534 actively exploited?
CVE-2026-10534 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 69.1% of all scored CVEs.
What is the CVSS score of CVE-2026-10534?
CVE-2026-10534 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-10534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10534, 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-10534

Explore →

Is Your Infrastructure Affected by CVE-2026-10534?

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