CVE-2026-18099

HIGHNVD 5.48.9▲
EchelonGraph scoreMEDIUM confidence

Score 8.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. NVD baseline CVSS 5.4; sources differ by 3.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: 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 execute arbitrary script code due to improper neutralization of user-controlled input.

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

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Navigator for i

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

Vendor Advisories for CVE-2026-18099(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 30× in last 7d / 39× 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 23:09 UTCEG score recompute
  2. 2026-08-20 23:09 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 10:18 UTCGHSA enrichment
  5. 2026-08-19 21:27 UTCEG score recompute
  6. 2026-08-19 21:27 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 08:34 UTCGHSA enrichment
  9. 2026-08-18 19:41 UTCEG score recompute
  10. 2026-08-18 19:41 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 06:50 UTCGHSA enrichment
  13. 2026-08-17 17:56 UTCEG score recompute
  14. 2026-08-17 17:56 UTCGHSA enrichment
  15. 2026-08-17 17:52 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  16. 2026-08-17 17:02 UTCEG score recompute
  17. 2026-08-17 17:02 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 04:11 UTCGHSA enrichment
  20. 2026-08-16 15:20 UTCEG score recompute
  21. 2026-08-16 15:20 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:29 UTCEG score recompute
  24. 2026-08-16 02:29 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 14 more
  1. 2026-08-15 13:38 UTCEG score recompute
  2. 2026-08-15 13:38 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:46 UTCGHSA enrichment
  5. 2026-08-14 11:55 UTCGHSA enrichment
  6. 2026-08-13 23:04 UTCEG score recompute
  7. 2026-08-13 23:04 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 10:12 UTCEG score recompute
  10. 2026-08-13 10:12 UTCGHSA enrichment
  11. 2026-08-12 21:21 UTCEG score recompute
  12. 2026-08-12 20:19 UTCEG score recompute
  13. 2026-08-12 19:46 UTCEG score recompute
  14. 2026-08-12 19:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18099?
CVE-2026-18099 is a high vulnerability published on August 12, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute arbitrary script code due to improper neutralization of user-controlled input.
When was CVE-2026-18099 disclosed?
CVE-2026-18099 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-18099 actively exploited?
CVE-2026-18099 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 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-18099?
CVE-2026-18099 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2026-18099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18099, 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-18099

Explore →

Is Your Infrastructure Affected by CVE-2026-18099?

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

Start Free Scan →Browse All CVEs