Service interruption via DHCPv6 stack buffer overwrite
Published Jun 23, 2026 · Updated Jun 23, 2026
Stack out-of-bounds write in dhcpcd 10.3.2 and earlier allows remote attackers to interrupt the service via DHCPv6. In dhcp6_makemessage(), serialization of an RFC 6603 prefix-exclusion body can place 17 bytes into a 16-byte stack buffer. The crafted ADVERTISE must arrive from the same IPv6 link while the client processes delegated-prefix data; the overwrite corrupts adjacent stack memory and interrupts dhcpcd.
Summary
What happened
Stack out-of-bounds write in dhcpcd 10.3.2 and earlier allows remote attackers to interrupt the service via DHCPv6. In dhcp6_makemessage(), serialization of an RFC 6603 prefix-exclusion body can place 17 bytes into a 16-byte stack buffer. The crafted ADVERTISE must arrive from the same IPv6 link while the client processes delegated-prefix data; the overwrite corrupts adjacent stack memory and interrupts dhcpcd.
The record
- CVE
- CVE-2026-56114
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Network Configuration
- Product
- dhcpcd
- Classifications
- CWE-787, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=10.3.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo