CVE-2026-17274

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-04. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
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 bypass security restrictions due to predictable server seeds.

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

Published

September 4, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Debug Server

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

Vendor Advisories for CVE-2026-17274(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 17× in last 7d / 44× 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-09-19 09:04 UTCEG score recompute
  2. 2026-09-19 09:04 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 07:01 UTCEG score recompute
  5. 2026-09-18 07:01 UTCGHSA enrichment
  6. 2026-09-17 04:57 UTCEG score recompute
  7. 2026-09-17 04:57 UTCGHSA enrichment
  8. 2026-09-16 14:07 UTCEPSS rescore
  9. 2026-09-16 05:14 UTCEPSS rescore
  10. 2026-09-16 02:53 UTCEG score recompute
  11. 2026-09-16 02:53 UTCGHSA enrichment
  12. 2026-09-15 00:49 UTCGHSA enrichment
  13. 2026-09-13 22:45 UTCEG score recompute
  14. 2026-09-13 22:45 UTCGHSA enrichment
  15. 2026-09-13 16:46 UTCEPSS rescore
  16. 2026-09-12 20:42 UTCEG score recompute
  17. 2026-09-12 20:42 UTCGHSA enrichment
  18. 2026-09-12 15:00 UTCEPSS rescore
  19. 2026-09-11 18:39 UTCEG score recompute
  20. 2026-09-11 18:39 UTCGHSA enrichment
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-11 09:36 UTCEPSS rescore
  23. 2026-09-10 16:35 UTCEG score recompute
  24. 2026-09-10 16:35 UTCGHSA enrichment
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 19 more
  1. 2026-09-09 14:31 UTCEG score recompute
  2. 2026-09-09 14:31 UTCGHSA enrichment
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-08 19:57 UTCEG score recompute
  5. 2026-09-08 19:57 UTCGHSA enrichment
  6. 2026-09-08 18:16 UTCEG score recompute
  7. 2026-09-08 18:16 UTCGHSA enrichment
  8. 2026-09-08 15:13 UTCGHSA enrichment
  9. 2026-09-07 23:40 UTCEG score recompute
  10. 2026-09-07 23:40 UTCGHSA enrichment
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 21:35 UTCEG score recompute
  13. 2026-09-06 21:35 UTCGHSA enrichment
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-05 19:29 UTCEG score recompute
  16. 2026-09-05 19:29 UTCGHSA enrichment
  17. 2026-09-04 17:26 UTCEG score recompute
  18. 2026-09-04 16:39 UTCEG score recompute
  19. 2026-09-04 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17274?
CVE-2026-17274 is a medium vulnerability published on September 4, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to bypass security restrictions due to predictable server seeds.
When was CVE-2026-17274 disclosed?
CVE-2026-17274 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17274 actively exploited?
CVE-2026-17274 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-17274?
CVE-2026-17274 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-17274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17274, 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-17274

Explore →

Is Your Infrastructure Affected by CVE-2026-17274?

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

Start Free Scan →Browse All CVEs