Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-11232Invalid characters cause assert

Description

To trigger the issue, three configuration parameters must have specific settings: "hostname-char-set" must be left at the default setting, which is "[^A-Za-z0-9.-]"; "hostname-char-replacement" must be empty (the default); and "ddns-qualifying-suffix" must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.

Timeline

  1. ID reserved

    By isc

  2. · 28 days later

    Published

  3. · 6 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

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

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

Affected products

  • ISC · Kea

    • affected 3.0.1 – ≤ 3.0.1
    • affected 3.1.1 – ≤ 3.1.2
    • unaffected 2.6.0 – ≤ 2.6.4
    • unaffected 2.7.0 – ≤ 2.7.9
    • unaffected 3.0.0 – ≤ 3.0.0
    • unaffected 3.1.0 – ≤ 3.1.0

What to do

Solution: Upgrade to the patched release most closely related to your current version of Kea: 3.0.2 or 3.1.3.

Workaround: Setting "hostname-char-replacement" to anything other than an empty value (suggestion: "x") is an effective workaround to this issue, regardless of other settings.

Exploitation: We are not aware of any active exploits.

References

References2

Sources

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

Badge for a README or a ticket

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

Record last updated .