Skip to main content
CVE-2025-11232VulnerabilityPublished Updated

To trigger the issue, three configuration parameters must have specific settings: "hostname-char-set" must be left at

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-11232· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 4 Nov 2026, 18:00 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 4 Nov 2026.

What to do

AI-suggested

Until a fix is available, administrators should review and adjust the relevant configuration parameters to avoid the vulnerable combination: do not leave "hostname-char-set" at the default, ensure "hostname-char-replacement" is not empty, or keep "ddns-qualifying-suffix" empty. Monitoring for updates from the vendor is recommended.

Description

A vulnerability in Kea DHCP versions 3.0.1 and 3.1.1 through 3.1.2 can cause the kea-dhcp4 service to exit unexpectedly when specific configuration parameters are set to particular values. The issue requires "hostname-char-set" to be at its default value "[^A-Za-z0-9.-]", "hostname-char-replacement" to be empty, and "ddns-qualifying-suffix" to be non-empty. This can be triggered by a client sending certain option content, leading to a denial of service condition.

References

Community reviews

Loading reviews…