CVE-2026-3608 | Stack overflow in Kea daemons

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.

Published: 2026-03-25 Last update: 2026-03-25 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-3608 is rated Low Risk (31.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-3608

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-25 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-3608

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-3608

OS Trackers for CVE-2026-3608

vendor priority summary link
debian not yet assigned CVE-2026-3608 not yet assigned priority: Debian including 1 source packages (isc-kea), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-3608
redhat high — https://access.redhat.com/security/cve/CVE-2026-3608
suse high CVE-2026-3608 severity important: SUSE including 90 source package names (kea-2.6.5-150700.3.6.1, kea-3.0.3-1.1, …), 201 product×package rows across 29 product lines (Container suse/sl-micro/6.0/toolbox, Image SL-Micro, … (29 product lines)): Fixed 171, First Fixed 30. https://www.suse.com/security/cve/CVE-2026-3608/
ubuntu medium CVE-2026-3608 medium priority: Ubuntu including 1 source packages (isc-kea), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 6, released 1. https://ubuntu.com/security/CVE-2026-3608

Affected software / configurations for CVE-2026-3608

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-3608

cvelogic Threat Intelligence