CVE-2026-16967

HIGHNVD 7.58.5▲
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. NVD baseline CVSS 7.5; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.5EG
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.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 gain unauthorized access to system objects due to a time-of-check to time-of-use (TOCTOU) race condition involving symbolic links.

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

Published

August 13, 2026

Last Modified

August 17, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Multiple SQL Vulnerabilities [CVE-2026-16908, CVE-2026-16967]

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

Vendor Advisories for CVE-2026-16967(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 30× in last 7d / 37× 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:55 UTCEPSS rescore
  2. 2026-08-20 19:33 UTCGHSA enrichment
  3. 2026-08-20 07:00 UTCGHSA enrichment
  4. 2026-08-19 18:27 UTCEG score recompute
  5. 2026-08-19 18:27 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 05:39 UTCGHSA enrichment
  8. 2026-08-18 17:04 UTCEG score recompute
  9. 2026-08-18 17:04 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 04:02 UTCGHSA enrichment
  12. 2026-08-17 15:28 UTCEG score recompute
  13. 2026-08-17 15:28 UTCGHSA enrichment
  14. 2026-08-17 15:28 UTCNVD updateCVSS v3 → 7.5
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 04:13 UTCGHSA enrichment
  17. 2026-08-16 15:39 UTCEG score recompute
  18. 2026-08-16 15:39 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 03:06 UTCEG score recompute
  21. 2026-08-16 03:06 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 14:33 UTCGHSA enrichment
  24. 2026-08-15 01:59 UTCEG score recompute
  25. 2026-08-15 01:59 UTCGHSA enrichment
Show 12 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 13:26 UTCEG score recompute
  3. 2026-08-14 13:26 UTCGHSA enrichment
  4. 2026-08-14 12:49 UTCEG score recompute
  5. 2026-08-14 12:49 UTCGHSA enrichment
  6. 2026-08-14 05:24 UTCEG score recompute
  7. 2026-08-14 05:24 UTCGHSA enrichment
  8. 2026-08-14 04:24 UTCEG score recompute
  9. 2026-08-14 04:24 UTCGHSA enrichment
  10. 2026-08-13 20:20 UTCEG score recompute
  11. 2026-08-13 20:02 UTCEG score recompute
  12. 2026-08-13 20:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16967?
CVE-2026-16967 is a high vulnerability published on August 13, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to system objects due to a time-of-check to time-of-use (TOCTOU) race condition involving symbolic links.
When was CVE-2026-16967 disclosed?
CVE-2026-16967 was first published in the National Vulnerability Database on August 13, 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-16967 actively exploited?
CVE-2026-16967 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 82.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16967?
CVE-2026-16967 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2026-16967?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16967, 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-16967

Explore →

Is Your Infrastructure Affected by CVE-2026-16967?

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

Start Free Scan →Browse All CVEs