CVE-2026-17445

HIGHNVD 6.58.2▲
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. NVD baseline CVSS 6.5; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: 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 bypass security restrictions due to improper validation of an attacker-supplied user profile name.

CVSS v3
6.5
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
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 Improper Validation Vulnerability in Line Printer Daemon [CVE-2026-17445]

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

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

Frequently asked(5)

What is CVE-2026-17445?
CVE-2026-17445 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 bypass security restrictions due to improper validation of an attacker-supplied user profile name.
When was CVE-2026-17445 disclosed?
CVE-2026-17445 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-17445 actively exploited?
CVE-2026-17445 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 85.0% of all scored CVEs.
What is the CVSS score of CVE-2026-17445?
CVE-2026-17445 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.
How do I remediate CVE-2026-17445?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17445, 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-17445

Explore →

Is Your Infrastructure Affected by CVE-2026-17445?

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

Start Free Scan →Browse All CVEs