An integer underflow was found in the DHCPv4 packet capture code of wicked. ni_capture_inspect_udp_header() in src/capture.c does not verify that the IP total length field (ip_len) is at least as large as the IP header length (ihl) before subtracting the header length. An unauthenticated attacker on the same network can thereby trigger an out-of-bounds read past the receive buffer in the wicked DHCPv4 client (wickedd-dhcp4), which can crash the daemon depending on the process memory layout. No information disclosure has been demonstrated. This issue affects wicked up to and including version 0.6.80.
CVE-2026-71401
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% 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).
- 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
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 27, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026capture: fix two OOB reads in ni_capture_inspect_udp_header
Fix merged in openSUSE/wicked PR #1079 on 2026-08-27 — awaiting tagged release
https://github.com/openSUSE/wicked/pull/1079Vendor Advisories for CVE-2026-71401(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 12× in last 7d / 12× 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-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:51 UTCGHSA enrichment
- 2026-08-28 23:53 UTCEG score recompute
- 2026-08-28 23:53 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:27 UTCGHSA enrichment
- 2026-08-27 20:17 UTCEG score recompute
- 2026-08-27 20:17 UTCGHSA enrichment
- 2026-08-27 17:24 UTCEG score recompute
- 2026-08-27 16:47 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71401?
When was CVE-2026-71401 disclosed?
Is CVE-2026-71401 actively exploited?
What is the CVSS score of CVE-2026-71401?
How do I remediate CVE-2026-71401?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71401
Is Your Infrastructure Affected by CVE-2026-71401?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.