CVE-2026-17418

HIGHNVD 7.88.5▲
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. NVD baseline CVSS 7.8; sources differ by 0.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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 local authenticated attacker to cause a denial of service due to improper neutralization of special elements used in an SQL command.

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

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in SQL

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

Vendor Advisories for CVE-2026-17418(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 28× in last 7d / 41× 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:26 UTCEG score recompute
  2. 2026-08-21 06:26 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 18:29 UTCGHSA enrichment
  5. 2026-08-20 06:33 UTCGHSA enrichment
  6. 2026-08-19 18:36 UTCEG score recompute
  7. 2026-08-19 18:36 UTCGHSA enrichment
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 05:18 UTCGHSA enrichment
  10. 2026-08-18 17:20 UTCEG score recompute
  11. 2026-08-18 17:20 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 04:25 UTCGHSA enrichment
  14. 2026-08-17 16:29 UTCEG score recompute
  15. 2026-08-17 16:29 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 04:18 UTCGHSA enrichment
  18. 2026-08-16 16:21 UTCEG score recompute
  19. 2026-08-16 16:21 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:24 UTCEG score recompute
  22. 2026-08-16 04:24 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 16:28 UTCGHSA enrichment
  25. 2026-08-15 04:32 UTCEG score recompute
Show 16 more
  1. 2026-08-15 04:32 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 16:35 UTCGHSA enrichment
  4. 2026-08-14 04:34 UTCEG score recompute
  5. 2026-08-14 04:34 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 16:37 UTCEG score recompute
  8. 2026-08-13 16:37 UTCGHSA enrichment
  9. 2026-08-13 16:37 UTCNVD updateCVSS v3 → 7.8
  10. 2026-08-13 08:57 UTCGHSA enrichment
  11. 2026-08-12 21:01 UTCEG score recompute
  12. 2026-08-12 21:01 UTCGHSA enrichment
  13. 2026-08-12 18:18 UTCEG score recompute
  14. 2026-08-12 18:11 UTCEG score recompute
  15. 2026-08-12 17:26 UTCEG score recompute
  16. 2026-08-12 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17418?
CVE-2026-17418 is a high vulnerability published on August 12, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local authenticated attacker to cause a denial of service due to improper neutralization of special elements used in an SQL command.
When was CVE-2026-17418 disclosed?
CVE-2026-17418 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17418 actively exploited?
CVE-2026-17418 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 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-17418?
CVE-2026-17418 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2026-17418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17418, 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-17418

Explore →

Is Your Infrastructure Affected by CVE-2026-17418?

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

Start Free Scan →Browse All CVEs