{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71402 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-71402 is a medium-severity vulnerability in SUSE wicked, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71402 and fix it if it is affected.\n\nWhat it is: CVE-2026-71402 is a medium-severity vulnerability in SUSE wicked, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71402 in the wild and no public exploit code.\n\nAffected product: SUSE wicked. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-71402/ (Markdown: https://insights.sbomify.com/CVE-2026-71402/index.md)","id":"CVE-2026-71402","markdown":"https://insights.sbomify.com/CVE-2026-71402/index.md","name":"CVE-2026-71402","record":{"aliases":["GHSA-qwmv-r6fq-g9r3"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux network configuration","requires_auth":"none","summary":"An attacker on the same network can trigger an out-of-bounds read in wicked's DHCP client, potentially leaking heap memory contents into lease fields.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wicked: out-of-bounds read in the DHCPv4 option parser due to payload length taken from the IP total length","id":"CVE-2026-71402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Rancher: Identity-field mutation in /v3/users allows account hijack via principal rebind","id":"CVE-2026-71403"},"packages":[],"prev":{"headline":"wicked: integer underflow of the UDP length in ni_capture_inspect_udp_header() leads to an out-of-bounds read","id":"CVE-2026-71401"},"products":["wicked"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["SUSE"]},"summary":"An attacker on the same network can trigger an out-of-bounds read in wicked's DHCP client, potentially leaking heap memory contents into lease fields.","url":"https://insights.sbomify.com/CVE-2026-71402/"}