Nmap through 7.99 does not keep the IPv6 extension-header walk within the captured packet in ipv6_get_data_primitive (libnetutil/netutil.cc), so the pointer advances past the buffer and the remaining-length computation underflows to a large value. A scanned target or on-path attacker returning a crafted IPv6 response with a truncated extension header can trigger out-of-bounds reads and a crash during raw IPv6 scans.
CVE-2026-58058
Score 6.5 from GitHub Security Advisory published 2026-06-28. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 60(Attend)EG Risk 60/100SSVC: Attend
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 computedSeverity65% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 20.0%
- KEV
- Not listed
Published
June 28, 2026
Last Modified
June 30, 2026
Advisory Details (4)
Auto-updated Jun 28, 2026Nmap - Integer Underflow in IPv6 Extension Header Parsing | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nmap-integer-underflow-in-ipv6-extension-header-parsingcommit bb6754e76bb1 (nmap/nmap)
Fix landed in nmap/nmap commit bb6754e76bb1 — awaiting tagged release
https://github.com/nmap/nmap/commit/bb6754e76bb1686315008e1aa1c40202a513fb83exploitarium/nmap-ipv6-extlen-wrap-poc at main · bikini/exploitarium · GitHub
https://github.com/bikini/exploitarium/tree/main/nmap-ipv6-extlen-wrap-pocVendor Advisories for CVE-2026-58058(2)
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 11× in last 7d / 69× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 16:04 UTCVendor advisory
- 2026-07-16 16:04 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 15:15 UTCVendor advisory
- 2026-07-15 15:15 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 14:29 UTCVendor advisory
- 2026-07-14 14:28 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 13:44 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
Show 44 moreShow fewer
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 12:59 UTCVendor advisory
- 2026-07-12 12:59 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 12:16 UTCVendor advisory
- 2026-07-11 12:15 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 11:32 UTCVendor advisory
- 2026-07-10 11:32 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 10:46 UTCVendor advisory
- 2026-07-09 10:46 UTCGHSA enrichment
- 2026-07-08 10:03 UTCVendor advisory
- 2026-07-08 10:02 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 09:19 UTCVendor advisory
- 2026-07-07 09:19 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 08:35 UTCVendor advisory
- 2026-07-06 08:34 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 07:44 UTCVendor advisory
- 2026-07-05 07:43 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:58 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 05:53 UTCGHSA enrichment
- 2026-07-02 05:09 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 04:26 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 03:38 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 02:53 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 02:10 UTCEG score recompute
- 2026-06-28 02:09 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-191
Frequently asked(5)
What is CVE-2026-58058?
When was CVE-2026-58058 disclosed?
Is CVE-2026-58058 actively exploited?
What is the CVSS score of CVE-2026-58058?
How do I remediate CVE-2026-58058?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58058
Is Your Infrastructure Affected by CVE-2026-58058?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.