CVE-2025-32801 | 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: 2025-05-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-32801 is rated Low Risk (36.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.23%). 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-2025-32801

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-06-15 0.04% 0.23% +0.18%
2 2026-04-07 0.06% 0.04% -0.02%
3 2026-03-31 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32801

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2025-32801

OS Trackers for CVE-2025-32801

vendor priority summary link
alpine high CVE-2025-32801: 1 source package rows (kea); 9 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 2, open 7. https://security.alpinelinux.org/vuln/CVE-2025-32801
debian not yet assigned CVE-2025-32801 not yet assigned priority: Debian including 1 source packages (isc-kea), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 3, open 1. https://security-tracker.debian.org/tracker/CVE-2025-32801
redhat high — https://access.redhat.com/security/cve/CVE-2025-32801
suse high CVE-2025-32801 severity important: SUSE including 114 source package names (kea-2.6.3-1.1, kea-2.6.3-150600.13.6.1, …), 170 product×package rows across 7 product lines (SUSE Linux Enterprise Module for Basesystem 15 SP7, SUSE Linux Enterprise Module for Server Applications 15 SP7, … (7 product lines)): Fixed 170. https://www.suse.com/security/cve/CVE-2025-32801/
ubuntu medium CVE-2025-32801 medium priority: Ubuntu including 1 source packages (isc-kea), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): not-affected 5, ignored 3, released 1. https://ubuntu.com/security/CVE-2025-32801

Affected software / configurations for CVE-2025-32801

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-32801

cvelogic Threat Intelligence