CVE-2026-17218

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-12. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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: 1%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 could allow a remote attacker to execute arbitrary code due to an out-of-bounds write.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Remote Code Execution Vulnerability in Line Printer Daemon [CVE-2026-17218]

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

Vendor Advisories for CVE-2026-17218(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 56× in last 7d / 75× 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:42 UTCGHSA enrichment
  2. 2026-08-21 01:48 UTCEG score recompute
  3. 2026-08-21 01:48 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 21:51 UTCGHSA enrichment
  6. 2026-08-20 17:58 UTCGHSA enrichment
  7. 2026-08-20 14:05 UTCGHSA enrichment
  8. 2026-08-20 10:11 UTCGHSA enrichment
  9. 2026-08-20 06:17 UTCGHSA enrichment
  10. 2026-08-20 02:24 UTCGHSA enrichment
  11. 2026-08-19 22:30 UTCGHSA enrichment
  12. 2026-08-19 18:36 UTCEG score recompute
  13. 2026-08-19 18:36 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 14:36 UTCGHSA enrichment
  16. 2026-08-19 10:41 UTCGHSA enrichment
  17. 2026-08-19 06:48 UTCGHSA enrichment
  18. 2026-08-19 02:55 UTCGHSA enrichment
  19. 2026-08-18 23:00 UTCGHSA enrichment
  20. 2026-08-18 19:07 UTCGHSA enrichment
  21. 2026-08-18 15:13 UTCEG score recompute
  22. 2026-08-18 15:13 UTCGHSA enrichment
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-18 10:50 UTCGHSA enrichment
  25. 2026-08-18 06:56 UTCGHSA enrichment
Show 50 more
  1. 2026-08-18 03:03 UTCGHSA enrichment
  2. 2026-08-17 23:08 UTCGHSA enrichment
  3. 2026-08-17 19:13 UTCGHSA enrichment
  4. 2026-08-17 13:54 UTCEG score recompute
  5. 2026-08-17 13:54 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:00 UTCGHSA enrichment
  8. 2026-08-17 06:07 UTCGHSA enrichment
  9. 2026-08-17 02:14 UTCGHSA enrichment
  10. 2026-08-16 22:21 UTCGHSA enrichment
  11. 2026-08-16 18:28 UTCEG score recompute
  12. 2026-08-16 18:28 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 14:34 UTCGHSA enrichment
  15. 2026-08-16 10:40 UTCGHSA enrichment
  16. 2026-08-16 06:47 UTCGHSA enrichment
  17. 2026-08-16 02:54 UTCEG score recompute
  18. 2026-08-16 02:54 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 23:01 UTCGHSA enrichment
  21. 2026-08-15 19:08 UTCGHSA enrichment
  22. 2026-08-15 15:15 UTCGHSA enrichment
  23. 2026-08-15 11:22 UTCGHSA enrichment
  24. 2026-08-15 07:29 UTCGHSA enrichment
  25. 2026-08-15 03:36 UTCEG score recompute
  26. 2026-08-15 03:36 UTCGHSA enrichment
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-14 23:43 UTCGHSA enrichment
  29. 2026-08-14 19:50 UTCGHSA enrichment
  30. 2026-08-14 15:57 UTCGHSA enrichment
  31. 2026-08-14 12:03 UTCGHSA enrichment
  32. 2026-08-14 08:10 UTCGHSA enrichment
  33. 2026-08-14 04:17 UTCGHSA enrichment
  34. 2026-08-14 00:24 UTCEG score recompute
  35. 2026-08-14 00:24 UTCGHSA enrichment
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-13 20:30 UTCGHSA enrichment
  38. 2026-08-13 16:37 UTCGHSA enrichment
  39. 2026-08-13 12:34 UTCGHSA enrichment
  40. 2026-08-13 08:39 UTCGHSA enrichment
  41. 2026-08-13 04:46 UTCGHSA enrichment
  42. 2026-08-13 00:53 UTCGHSA enrichment
  43. 2026-08-12 21:00 UTCGHSA enrichment
  44. 2026-08-12 20:20 UTCEG score recompute
  45. 2026-08-12 20:20 UTCGHSA enrichment
  46. 2026-08-12 19:22 UTCEG score recompute
  47. 2026-08-12 19:22 UTCGHSA enrichment
  48. 2026-08-12 18:18 UTCEG score recompute
  49. 2026-08-12 17:51 UTCEG score recompute
  50. 2026-08-12 17:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17218?
CVE-2026-17218 is a critical vulnerability published on August 12, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code due to an out-of-bounds write.
When was CVE-2026-17218 disclosed?
CVE-2026-17218 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-17218 actively exploited?
CVE-2026-17218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.6% of all scored CVEs.
What is the CVSS score of CVE-2026-17218?
CVE-2026-17218 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-17218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17218, 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-17218

Explore →

Is Your Infrastructure Affected by CVE-2026-17218?

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

Start Free Scan →Browse All CVEs