CVE-2026-58081

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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: cisa-adp, epss
9.8EG
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.8Exploit: None knownExposed: 0

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

Several encoding modules, including HZ, UTF-7, VIQR, and ZW, did not properly check the size of the caller-supplied output buffer before writing converted characters.

An application that uses iconv(3) to convert untrusted input to or from one of the affected encodings may be vulnerable to buffer overflows if it uses one of the affected encoding modules.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
No patch confirmed yet.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 51× 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-20 20:56 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 18:34 UTCEG score recompute
  4. 2026-09-18 21:46 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 21:34 UTCEG score recompute
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 14:41 UTCEG score recompute
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 05:53 UTCEG score recompute
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 03:35 UTCEG score recompute
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-13 20:15 UTCEG score recompute
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-12 18:39 UTCEG score recompute
  17. 2026-09-11 16:40 UTCEG score recompute
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 13:00 UTCEG score recompute
  20. 2026-09-10 12:19 UTCEG score recompute
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-09 02:43 UTCEG score recompute
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-07 19:24 UTCEG score recompute
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 32 more
  1. 2026-09-06 16:18 UTCEG score recompute
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-05 18:18 UTCEG score recompute
  4. 2026-09-04 15:04 UTCEG score recompute
  5. 2026-09-04 07:43 UTCEG score recompute
  6. 2026-09-04 05:07 UTCEPSS rescore
  7. 2026-09-02 16:07 UTCEG score recompute
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:56 UTCEG score recompute
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 06:25 UTCEG score recompute
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 19:49 UTCEG score recompute
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:27 UTCEG score recompute
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-29 02:30 UTCEG score recompute
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-27 16:32 UTCEG score recompute
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 18:02 UTCEG score recompute 9.80
  22. 2026-08-26 18:01 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 08:32 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-20 22:55 UTCEPSS rescore
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 08:20 UTCNVD update
  31. 2026-08-19 07:28 UTCEG score recompute
  32. 2026-08-19 07:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58081?
CVE-2026-58081 is a critical vulnerability published on August 19, 2026. Several encoding modules, including HZ, UTF-7, VIQR, and ZW, did not properly check the size of the caller-supplied output buffer before writing converted characters. An application that uses iconv(3) to convert untrusted input to or from one of the affected encodings may be vulnerable to buffer…
When was CVE-2026-58081 disclosed?
CVE-2026-58081 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58081 actively exploited?
CVE-2026-58081 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 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-58081?
CVE-2026-58081 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-58081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58081, 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-58081

Explore →

Is Your Infrastructure Affected by CVE-2026-58081?

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