CVE-2026-16815

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: 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 cause a denial of service and potentially obtain sensitive information due to a stack-based buffer overflow.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
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 Vulnerabilities in Simple Mail Transfer Protocol

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

Vendor Advisories for CVE-2026-16815(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 49× in last 7d / 52× 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:21 UTCGHSA enrichment
  2. 2026-08-21 01:31 UTCEG score recompute
  3. 2026-08-21 01:31 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 21:42 UTCGHSA enrichment
  6. 2026-08-20 17:52 UTCGHSA enrichment
  7. 2026-08-20 14:03 UTCGHSA enrichment
  8. 2026-08-20 09:43 UTCGHSA enrichment
  9. 2026-08-20 05:54 UTCGHSA enrichment
  10. 2026-08-20 02:05 UTCGHSA enrichment
  11. 2026-08-19 22:16 UTCGHSA enrichment
  12. 2026-08-19 18:27 UTCEG score recompute
  13. 2026-08-19 18:27 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 14:07 UTCGHSA enrichment
  16. 2026-08-19 10:18 UTCGHSA enrichment
  17. 2026-08-19 06:29 UTCGHSA enrichment
  18. 2026-08-19 02:39 UTCGHSA enrichment
  19. 2026-08-18 22:47 UTCGHSA enrichment
  20. 2026-08-18 18:49 UTCGHSA enrichment
  21. 2026-08-18 14:59 UTCEG score recompute
  22. 2026-08-18 14:59 UTCGHSA enrichment
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-18 10:28 UTCGHSA enrichment
  25. 2026-08-18 06:39 UTCGHSA enrichment
Show 27 more
  1. 2026-08-18 02:50 UTCGHSA enrichment
  2. 2026-08-17 23:00 UTCGHSA enrichment
  3. 2026-08-17 19:10 UTCGHSA enrichment
  4. 2026-08-17 14:56 UTCEG score recompute▲ 0.50
  5. 2026-08-17 14:56 UTCGHSA enrichment
  6. 2026-08-17 14:56 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 03:58 UTCGHSA enrichment
  9. 2026-08-16 16:17 UTCEG score recompute
  10. 2026-08-16 16:17 UTCGHSA enrichment
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 04:37 UTCEG score recompute
  13. 2026-08-16 04:37 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 16:56 UTCGHSA enrichment
  16. 2026-08-15 05:15 UTCEG score recompute
  17. 2026-08-15 05:15 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 17:34 UTCEG score recompute
  20. 2026-08-14 17:34 UTCGHSA enrichment
  21. 2026-08-14 17:07 UTCEG score recompute
  22. 2026-08-14 17:07 UTCGHSA enrichment
  23. 2026-08-14 08:22 UTCEG score recompute
  24. 2026-08-14 08:22 UTCGHSA enrichment
  25. 2026-08-13 20:20 UTCEG score recompute
  26. 2026-08-13 19:47 UTCEG score recompute
  27. 2026-08-13 19:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16815?
CVE-2026-16815 is a critical vulnerability published on August 13, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to cause a denial of service and potentially obtain sensitive information due to a stack-based buffer overflow.
When was CVE-2026-16815 disclosed?
CVE-2026-16815 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-16815 actively exploited?
CVE-2026-16815 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 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16815?
CVE-2026-16815 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-16815?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16815, 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-16815

Explore →

Is Your Infrastructure Affected by CVE-2026-16815?

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

Start Free Scan →Browse All CVEs