An out-of-bounds read was found in the DHCPv4 packet capture code of wicked. ni_capture_inspect_udp_header() in src/capture.c reports the IP total length as the payload length instead of the length of the remaining UDP payload. Consequently, the DHCP option walker in the DHCPv4 client (wickedd-dhcp4) reads up to ihl + 8 bytes — at most 68 bytes — past the end of the 1500-byte packet receive buffer. An unauthenticated attacker on the same network who sends a crafted DHCP/UDP packet can make the client parse adjacent heap memory as DHCP options, so that heap contents such as allocator metadata or pointer values can be interpreted into lease fields. The over-read is bounded to 68 bytes; no memory write, no attacker control over the adjacent bytes and no remote exfiltration primitive has been demonstrated. This issue affects wicked up to and including version 0.6.80.
CVE-2026-71402
Score 5.4 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 5.4; 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
- 5.4
- EG Score
- 5.4(high)
- 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 computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- 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-71402(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
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:15 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-71402?
When was CVE-2026-71402 disclosed?
Is CVE-2026-71402 actively exploited?
What is the CVSS score of CVE-2026-71402?
How do I remediate CVE-2026-71402?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71402
Is Your Infrastructure Affected by CVE-2026-71402?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.