CVE-2026-16907

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6EG
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.6Exploit: 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 execute arbitrary code due to improper bounds checking.

CVSS v3
7.6
EG Score
7.6(high)
EG Risk
34(Track)
EG Risk 34/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
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
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 Multiple Vulnerabilities in the Debug Server

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

Vendor Advisories for CVE-2026-16907(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 33× 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 15:48 UTCGHSA enrichment
  2. 2026-08-20 03:41 UTCEG score recompute
  3. 2026-08-20 03:41 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 15:34 UTCGHSA enrichment
  6. 2026-08-19 03:22 UTCGHSA enrichment
  7. 2026-08-18 15:13 UTCEG score recompute
  8. 2026-08-18 15:13 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 01:35 UTCEG score recompute
  11. 2026-08-18 01:34 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 13:28 UTCEG score recompute
  14. 2026-08-17 13:28 UTCGHSA enrichment
  15. 2026-08-17 12:38 UTCEG score recompute
  16. 2026-08-17 12:38 UTCGHSA enrichment
  17. 2026-08-17 04:47 UTCGHSA enrichment
  18. 2026-08-16 16:40 UTCEG score recompute
  19. 2026-08-16 16:40 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:33 UTCEG score recompute
  22. 2026-08-16 04:33 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 16:27 UTCGHSA enrichment
  25. 2026-08-15 04:20 UTCEG score recompute
Show 15 more
  1. 2026-08-15 04:20 UTCGHSA enrichment
  2. 2026-08-15 04:13 UTCEG score recompute
  3. 2026-08-15 04:13 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 17:21 UTCGHSA enrichment
  6. 2026-08-14 05:04 UTCEG score recompute
  7. 2026-08-14 05:04 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 16:57 UTCGHSA enrichment
  10. 2026-08-13 09:07 UTCGHSA enrichment
  11. 2026-08-12 21:00 UTCEG score recompute
  12. 2026-08-12 21:00 UTCGHSA enrichment
  13. 2026-08-12 18:18 UTCEG score recompute
  14. 2026-08-12 17:51 UTCEG score recompute
  15. 2026-08-12 17:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16907?
CVE-2026-16907 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 execute arbitrary code due to improper bounds checking.
When was CVE-2026-16907 disclosed?
CVE-2026-16907 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-16907 actively exploited?
CVE-2026-16907 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 65.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16907?
CVE-2026-16907 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-16907?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16907, 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-16907

Explore →

Is Your Infrastructure Affected by CVE-2026-16907?

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

Start Free Scan →Browse All CVEs