CVE-2026-17111

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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 i 7.6, 7.5, 7.4, and 7.3 s vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

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
17%
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 i is Affected By Multiple Vulnerabilities in SQL

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

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

Frequently asked(5)

What is CVE-2026-17111?
CVE-2026-17111 is a critical vulnerability published on August 12, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 s vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
When was CVE-2026-17111 disclosed?
CVE-2026-17111 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-17111 actively exploited?
CVE-2026-17111 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 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-17111?
CVE-2026-17111 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-17111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17111, 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-17111

Explore →

Is Your Infrastructure Affected by CVE-2026-17111?

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

Start Free Scan →Browse All CVEs