Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2025-32802

Insecure handling of file paths allows multiple local attacks

Medium6.1EPSS 0.23%
Published
Updated
Reserved
Assigned by
isc

Description

Kea configuration and API directives can be used to overwrite arbitrary files, subject to permissions granted to Kea. 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.

Scores

CVSS scores of CVE-2025-32802, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Deferred3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS (exploitation in 30 days)
0.23% · top 87% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.1.

Weakness

Affected products

  • ISC · Kea

    • affected 2.4.0 – ≤ 2.4.1
    • affected 2.6.0 – ≤ 2.6.2
    • affected 2.7.0 – ≤ 2.7.8

What to do

Solution: Upgrade to the patched release most closely related to your current version of Kea: 2.4.2, 2.6.3, or 2.7.9.

Workaround: Two mitigation approaches are possible: (1) Disable the API entirely, by (1a) disabling the `kea-ctrl-agent`, and (1b) removing any `"control-socket"` stanzas from the Kea configuration files; or (2) Secure access to the API by (2a) requiring authentication (a password or client certificate) for the `kea-ctrl-agent`, and (2b) configuring all `"control-socket"` stanzas to use a directory restricted to only trusted users.

Exploitation: We are not aware of any active exploits.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-32802 badge
[![CVE-2025-32802](https://trackcve.app/badge/CVE-2025-32802.svg)](https://trackcve.app/cve/CVE-2025-32802)

Record last updated .