CVE-2026-16002

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The affected product is vulnerable to an Out-of-bounds read, which may allow an attacker to crash the parsing process and cause a denial of service.

CVSS v3
8.2
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
35%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

MZ Automation lib60870 | CISA

MZ Automation lib60870 | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/news-events/ics-advisories/icsa-26-204-07

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 54× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:28 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 22:46 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 19:54 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 16:22 UTCEG score recompute
  9. 2026-08-25 13:48 UTCEPSS rescore
  10. 2026-08-24 15:07 UTCEG score recompute
  11. 2026-08-23 00:39 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 12:01 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 10:26 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 20:30 UTCEG score recompute
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 18:57 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-18 01:26 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 23:37 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:00 UTCEG score recompute
Show 44 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 09:46 UTCEG score recompute
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 08:31 UTCEG score recompute
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-12 18:38 UTCEG score recompute
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-11 17:24 UTCEG score recompute
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 04:41 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-09 14:49 UTCEG score recompute
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-09 02:12 UTCEG score recompute
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-08 00:58 UTCEG score recompute
  17. 2026-08-06 23:43 UTCEG score recompute
  18. 2026-08-06 13:46 UTCEPSS rescore
  19. 2026-08-05 22:28 UTCEG score recompute
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 21:05 UTCEG score recompute
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 10:38 UTCEPSS rescore
  24. 2026-08-03 19:45 UTCEG score recompute
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 05:51 UTCEG score recompute
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 04:37 UTCEG score recompute
  29. 2026-08-01 04:15 UTCEPSS rescore
  30. 2026-07-31 03:19 UTCEG score recompute
  31. 2026-07-30 14:40 UTCEG score recompute
  32. 2026-07-30 08:21 UTCEG score recompute
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-28 18:19 UTCEG score recompute
  35. 2026-07-27 17:03 UTCEG score recompute
  36. 2026-07-27 14:13 UTCEPSS rescore
  37. 2026-07-26 15:44 UTCEG score recompute
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 03:06 UTCEG score recompute
  41. 2026-07-25 14:17 UTCEPSS rescore
  42. 2026-07-24 14:17 UTCEPSS rescore
  43. 2026-07-23 21:12 UTCEG score recompute
  44. 2026-07-23 21:11 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16002?
CVE-2026-16002 is a high vulnerability published on July 23, 2026. The affected product is vulnerable to an Out-of-bounds read, which may allow an attacker to crash the parsing process and cause a denial of service.
When was CVE-2026-16002 disclosed?
CVE-2026-16002 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16002 actively exploited?
CVE-2026-16002 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 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-16002?
CVE-2026-16002 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-16002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16002, 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-16002

Explore →

Is Your Infrastructure Affected by CVE-2026-16002?

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

Start Free Scan →Browse All CVEs