No exploitation reportedFix available

CVE-2025-32801

No exploitation reported by the sources we read.

Published2025-05-28
WeaknessCWE-94

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC

2025-05-2817:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-32801?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-32801?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

kea-docAlmaLinux:10all versions · fixed in 2.6.3-1.el10_0

Vendor advisories

CVE-2025-32801 Red Hat Product Security78 products fixed
kea: Loading a malicious hook library can lead to local privilege escalation
RHSA-2025:9178 Red Hat Product Security78 products fixed
Red Hat Security Advisory: kea security update

Full record on NVD

Fix

Vendor fix Red Hat Product Security RHSA-2025:9178 · 78 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Workaround from the vendor Red Hat Product Security RHSA-2025:9178 · 78 productsThis vulnerability can be mitigated via one of the two following alternatives: 1) Disable the Kea API entirely by disabling the kea-ctrl-agent and removing any control-socket stanzas from the Kea configuration files. 2) Configure the API to require authentication for the kea-ctrl-agent and config…

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVE recordread 2026-10-23
CISA-ADPSSVC decisionnone2025-05-28
OpenCVESSVC decisionnone—
CNACVSS 3.17.8read 2026-10-23
CNAweakness (CWE)CWE-94read 2026-10-23
FIRST EPSSEPSS score0.3 %2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published: 2025-05-28
Last Modified: 2026-06-17
NVD status: Deferred

Frequently asked questions

What is CVE-2025-32801?

Is CVE-2025-32801 actively exploited?

Active exploitation of CVE-2025-32801 has not been confirmed. Its EPSS score was 0.3% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-32801?

CVE-2025-32801 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running kea? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database