Skip to main content
VulnerabilityPublished

CVE-2025-32803: ISC Kea · Incorrect Default Permissions

Affects ISC KeaSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ISC KeaAffected
  • =2.4.0
  • =2.6.0
  • =2.7.0
  • =2.4.1
  • >=2.6.0 <=2.6.2
  • >=2.7.0 <=2.7.8
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should immediately audit the file permissions of Kea DHCP server log and lease files on all affected versions. Permissions should be restricted to the minimum necessary, typically allowing read/write access only to the Kea service user and administrators. Implementing strict access control lists (ACLs) or using filesystem-level security features such as SELinux or AppArmor can further restrict unauthorized access. Organizations should monitor local user activities and review system logs for any unauthorized access attempts. Where possible, upgrade to a fixed version of Kea once ISC releases a patch addressing this issue. Until a patch is available, consider isolating DHCP servers to trusted administrative environments with limited local user access. Additionally, employ network segmentation to limit exposure of DHCP servers and sensitive network infrastructure. Regular security audits and configuration management should be enforced to ensure permissions remain correctly set over time.

Description

In some cases, Kea log files or lease files may be world-readable. 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.

References

Community reviews

Loading reviews…