Sending a maliciously crafted message to the kea-ctrl-agent, kea-dhcp-ddns, kea-dhcp4, or kea-dhcp6 daemons over any configured API socket or HA listener can cause the receiving daemon to exit with a stack overflow error.
This issue affects Kea versions 2.6.0 through 2.6.4 and 3.0.0 through 3.0.2.
Security readout for executives and security teams
Plain-English summary
CVE-2026-3608 can crash ISC Kea DHCP-related daemons when they receive a maliciously crafted message through configured API sockets or HA listeners. The business impact is service availability: DHCP, DDNS, control-agent, or HA functions may stop until restarted. Affected versions are Kea 2.6.0-2.6.4 and 3.0.0-3.0.2.
Executive priority
Treat as high priority for DHCP infrastructure because successful exploitation can interrupt address assignment or related Kea services. Prioritize internet-facing, partner-reachable, or flat-network deployments first, then complete routine patching for all affected internal clusters.
Technical view
The issue is a stack overflow causing process exit in kea-ctrl-agent, kea-dhcp-ddns, kea-dhcp4, or kea-dhcp6. The CVSS 3.1 score is 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Public sources identify patched release branches at 2.6.5 and 3.0.3.
Likely exposure
Organizations running ISC Kea 2.6.0-2.6.4 or 3.0.0-3.0.2 are exposed where affected daemons accept traffic through configured API sockets or HA listeners, especially from untrusted or broadly reachable networks.
Exploitation context
The supplied sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability is remotely reachable per CVSS and requires no privileges or user interaction, but the documented impact is daemon crash and availability loss, not data theft or code execution.
Researcher notes
Evidence supports an availability-only denial-of-service flaw with no stated confidentiality or integrity impact. The bundle does not include proof-of-concept details, root-cause internals, or named workaround beyond upgrading and limiting listener exposure.
Mitigation direction
Upgrade affected Kea 2.6.x deployments to 2.6.5 or later vendor guidance.
Upgrade affected Kea 3.0.x deployments to 3.0.3 or later vendor guidance.
Restrict API socket and HA listener reachability to trusted administrative or cluster networks.
Monitor affected daemons and restart behavior until patched.
Review ISC and distribution advisories for platform-specific packages and errata.
Validation and detection
Inventory Kea versions and confirm whether 2.6.0-2.6.4 or 3.0.0-3.0.2 are present.
Identify enabled kea-ctrl-agent, kea-dhcp-ddns, kea-dhcp4, and kea-dhcp6 daemons.
Map configured API sockets and HA listeners to reachable networks and trust boundaries.
Check service logs for unexpected exits or stack overflow errors.
Confirm patched versions after upgrade through package or binary version reporting.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-617 · source CWE mapping
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.