CVE-2026-18193

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: 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 attacker to bypass security restrictions due to improper validation of user-controlled addresses.

CVSS v3
10.0
EG Score
10.0(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
Severity100% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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-18193(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 44× in last 7d / 47× 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 06:22 UTCGHSA enrichment
  2. 2026-08-21 02:18 UTCEG score recompute
  3. 2026-08-21 02:18 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:13 UTCGHSA enrichment
  6. 2026-08-20 18:08 UTCGHSA enrichment
  7. 2026-08-20 14:03 UTCGHSA enrichment
  8. 2026-08-20 09:06 UTCGHSA enrichment
  9. 2026-08-20 05:01 UTCGHSA enrichment
  10. 2026-08-20 00:56 UTCGHSA enrichment
  11. 2026-08-19 20:51 UTCEG score recompute
  12. 2026-08-19 20:51 UTCGHSA enrichment
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-19 16:46 UTCEG score recompute▲ 1.10
  15. 2026-08-19 16:46 UTCGHSA enrichment
  16. 2026-08-19 16:44 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  17. 2026-08-19 12:43 UTCGHSA enrichment
  18. 2026-08-18 23:40 UTCEG score recompute
  19. 2026-08-18 23:40 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-18 10:38 UTCGHSA enrichment
  22. 2026-08-17 21:35 UTCEG score recompute
  23. 2026-08-17 21:35 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 08:29 UTCGHSA enrichment
Show 22 more
  1. 2026-08-16 19:27 UTCEG score recompute
  2. 2026-08-16 19:27 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 06:24 UTCEG score recompute
  5. 2026-08-16 06:24 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 17:22 UTCGHSA enrichment
  8. 2026-08-15 04:20 UTCEG score recompute
  9. 2026-08-15 04:20 UTCGHSA enrichment
  10. 2026-08-15 04:13 UTCEG score recompute
  11. 2026-08-15 04:13 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 19:36 UTCGHSA enrichment
  14. 2026-08-14 19:17 UTCEG score recompute
  15. 2026-08-14 19:17 UTCGHSA enrichment
  16. 2026-08-14 18:34 UTCEG score recompute
  17. 2026-08-14 18:34 UTCGHSA enrichment
  18. 2026-08-14 10:24 UTCEG score recompute
  19. 2026-08-14 10:24 UTCGHSA enrichment
  20. 2026-08-13 21:21 UTCEG score recompute
  21. 2026-08-13 20:57 UTCEG score recompute
  22. 2026-08-13 20:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18193?
CVE-2026-18193 is a critical vulnerability published on August 13, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to bypass security restrictions due to improper validation of user-controlled addresses.
When was CVE-2026-18193 disclosed?
CVE-2026-18193 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-18193 actively exploited?
CVE-2026-18193 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 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-18193?
CVE-2026-18193 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-18193?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18193, 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-18193

Explore →

Is Your Infrastructure Affected by CVE-2026-18193?

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

Start Free Scan →Browse All CVEs