If a DHCPv4 client sends a request with some specific options, and Kea fails to find an appropriate subnet for the
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 4 Nov 2026, 17:57 UTC
Thin evidence
One scorer or none| CNA (isc) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
AI-suggested
Until a fix is available, avoid configurations or client requests that trigger the failure, such as unicast DHCPv4 requests with the specific problematic options. Monitor vendor communications for updates.
Description
A vulnerability in Kea DHCPv4 server versions 2.7.1 through 2.7.9, 3.0.0, and 3.1.0 causes the kea-dhcp4 process to abort with an assertion failure when it receives a unicast DHCPv4 request containing specific options and fails to find an appropriate subnet for the client. Broadcast requests do not trigger this issue.