CVE-2026-18249

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% 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.9EG
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.9Exploit: None knownExposed: 0

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

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain elevated privileges due to improper validation of pointers read from Java-controlled addresses.

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

Published

August 13, 2026

Last Modified

August 19, 2026

Advisory Details (1)

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

Security Bulletin: IBM i Is Affected By Multiple Vulnerabilities in IBM Java SDK and IBM Java Runtime

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

Vendor Advisories for CVE-2026-18249(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 45× 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-21 05:10 UTCGHSA enrichment
  2. 2026-08-21 01:31 UTCEG score recompute
  3. 2026-08-21 01:31 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 21:53 UTCGHSA enrichment
  6. 2026-08-20 18:15 UTCGHSA enrichment
  7. 2026-08-20 14:37 UTCGHSA enrichment
  8. 2026-08-20 10:59 UTCGHSA enrichment
  9. 2026-08-20 07:20 UTCGHSA enrichment
  10. 2026-08-20 03:42 UTCGHSA enrichment
  11. 2026-08-20 00:03 UTCGHSA enrichment
  12. 2026-08-19 20:25 UTCEG score recompute
  13. 2026-08-19 20:25 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 16:46 UTCEG score recompute▲ 1.50
  16. 2026-08-19 16:46 UTCGHSA enrichment
  17. 2026-08-19 16:44 UTCNVD updateCVSS v3 → 9.9 · severity → CRITICAL
  18. 2026-08-19 08:27 UTCGHSA enrichment
  19. 2026-08-18 20:02 UTCEG score recompute
  20. 2026-08-18 20:02 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-18 07:37 UTCGHSA enrichment
  23. 2026-08-17 19:10 UTCEG score recompute
  24. 2026-08-17 19:09 UTCGHSA enrichment
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 23 more
  1. 2026-08-17 06:02 UTCGHSA enrichment
  2. 2026-08-16 17:37 UTCEG score recompute
  3. 2026-08-16 17:37 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 05:10 UTCEG score recompute
  6. 2026-08-16 05:10 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 16:45 UTCGHSA enrichment
  9. 2026-08-15 04:20 UTCEG score recompute
  10. 2026-08-15 04:20 UTCGHSA enrichment
  11. 2026-08-15 04:13 UTCEG score recompute
  12. 2026-08-15 04:13 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 19:17 UTCGHSA enrichment
  15. 2026-08-14 16:32 UTCEG score recompute
  16. 2026-08-14 16:32 UTCGHSA enrichment
  17. 2026-08-14 16:04 UTCEG score recompute
  18. 2026-08-14 16:04 UTCGHSA enrichment
  19. 2026-08-14 09:46 UTCEG score recompute
  20. 2026-08-14 09:46 UTCGHSA enrichment
  21. 2026-08-13 21:21 UTCEG score recompute
  22. 2026-08-13 20:57 UTCEG score recompute
  23. 2026-08-13 20:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18249?
CVE-2026-18249 is a critical vulnerability published on August 13, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain elevated privileges due to improper validation of pointers read from Java-controlled addresses.
When was CVE-2026-18249 disclosed?
CVE-2026-18249 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18249 actively exploited?
CVE-2026-18249 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 79.9% of all scored CVEs.
What is the CVSS score of CVE-2026-18249?
CVE-2026-18249 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-18249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18249, 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-18249

Explore →

Is Your Infrastructure Affected by CVE-2026-18249?

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

Start Free Scan →Browse All CVEs