If a DHCPv4 client sends a request with some specific options, and Kea fails to find an appropriate subnet for the client, the `kea-dhcp4` process will abort with an assertion failure. This happens only if the client request is unicast directly to Kea; broadcast messages do not cause the problem. This issue affects Kea versions 2.7.1 through 2.7.9, 3.0.0, and 3.1.0.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Freebsd | — | Upgrade kea-develUpgrade kea | Dec 10, 2025 | Aug 27, 2025 |
| Oracle_linux | — | Upgrade kea-docUpgrade keaUpgrade kea-keamaUpgrade kea-libsUpgrade kea-hooks | Dec 5, 2025 | Aug 27, 2025 |
| Redhat_linux | — | Upgrade kea-docUpgrade kea-devel-debuginfoUpgrade kea-libsUpgrade kea-keama-debuginfoUpgrade kea-debugsourceUpgrade kea-keamaUpgrade keaUpgrade kea-debuginfoUpgrade kea-libs-debuginfoUpgrade kea-hooks-debuginfoUpgrade kea-hooks | Jan 27, 2026 | Aug 27, 2025 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub