# CVE-2025-32801: Loading a malicious hook library can lead to local privilege escalation

> Attackers can load malicious hook libraries via Kea API to achieve local privilege escalation, particularly when running as root with unsecured APIs.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2025
- **Updated:** 28 May 2025
- **Also known as:** ALPINE-CVE-2025-32801, DEBIAN-CVE-2025-32801, GHSA-hv8v-455m-2grc, UBUNTU-CVE-2025-32801

## What is CVE-2025-32801?

CVE-2025-32801 is a high-severity code injection vulnerability in ISC Kea, published on 28 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-32801?


## How do I fix CVE-2025-32801?

Upgrade to a fixed version.

## Is CVE-2025-32801 being exploited?

There is no known exploitation of CVE-2025-32801 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32801 and fix it if it is affected.

What it is: CVE-2025-32801 is a high-severity code injection vulnerability in ISC Kea, published on 28 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32801 in the wild and no public exploit code.

Affected product: ISC Kea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32801/ (Markdown: https://insights.sbomify.com/CVE-2025-32801/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32801
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32801
- OSV: https://osv.dev/vulnerability/CVE-2025-32801

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32801/
Summaries are generated and may contain mistakes; the official description above is the record.