Loading a malicious hook library can lead to local privilege escalation
Kea configuration and API directives can be used to load a malicious hook library. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure paths. This issue affects Kea versions 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8.
- Published
- May 28, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 16th percentile
- CWE
- CWE-94
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · isc
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.
ISC Kea
- 2.4.0 and later · up to and including 2.4.1affected
- 2.6.0 and later · up to and including 2.6.2affected
- 2.7.0 and later · up to and including 2.7.8affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kea-doc | before 2.6.3-1.el10_0 | 2.6.3-1.el10_0 |
| Alpine:v3.22 | kea | before 2.6.3-r0 | 2.6.3-r0 |
| Debian:12 | isc-kea | all versions | — |
| Debian:13 | isc-kea | before 2.6.3-1 | 2.6.3-1 |
| openSUSE:Tumbleweed | kea | before 2.6.3-1.1 | 2.6.3-1.1 |
| Red Hat:enterprise_linux:10.0 | kea | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-debuginfo | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-debugsource | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-doc | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-hooks | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-hooks-debuginfo | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-keama | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-keama-debuginfo | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-libs | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kea-libs-debuginfo | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| Rocky Linux:10 | kea | before 0:2.6.3-1.el10_0 | 0:2.6.3-1.el10_0 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kea | before 2.6.3-150700.3.3.5 | 2.6.3-150700.3.3.5 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | kea | before 2.6.3-150600.13.6.1 | 2.6.3-150600.13.6.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | kea | before 2.6.3-150600.13.6.1 | 2.6.3-150600.13.6.1 |
Same product
isc: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-5739Failure to release memory may exhaust system resources31Monitor
- CVE-2026-3608Stack overflow in Kea daemons30Monitor
- CVE-2025-11232Invalid characters cause assert30Monitor
- CVE-2025-40779Kea crash upon interaction between specific client options and subnet selection30Monitor
- CVE-2015-8373The kea-dhcp4 and kea-dhcp6 servers 0.9.2 and 1.0.0-beta in ISC Kea, when certain debugging settings are used, allow remote attackers to cau28Monitor
- CVE-2019-6474A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:kea-doc | 2.6.3-1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| alpine:kea | 2.6.3-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:isc-kea | 2.6.3-1 · Debian:13 | Package registry (OSV) |
| opensuse:kea | 2.6.3-150600.13.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:kea | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-debuginfo | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-debugsource | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-doc | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-hooks | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-hooks-debuginfo | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-keama | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-keama-debuginfo | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-libs | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kea-libs-debuginfo | 0:2.6.3-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| rocky linux:kea | 0:2.6.3-1.el10_0 · Rocky Linux:10 | Package registry (OSV) |
| suse:kea | 2.6.3-150600.13.6.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS | Package registry (OSV) |
| suse:kea | 2.6.3-150700.3.3.5 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.