Skip to main content
VulnerabilityPublished

CVE-2025-24528: MIT Kerberos 5 · Integer Overflow or Wraparound

Affects MIT Kerberos 5Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High : upgrade to 1.22 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.22
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jan 2026

  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

Upgrade MIT Kerberos 5 to 1.22.

Affected software

ProductAffectedFixed in
MITKerberos 5Affected
  • >=1.7 <1.22
Fixed in
  • 1.22
GitHubkrb5/krb5pkg:github/krb5/krb5Other threatsAffected
  • =1.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade MIT Kerberos 5 to version 1.22 or later as soon as the patch addressing CVE-2025-24528 is released. Monitor official MIT Kerberos project channels for patch announcements.
  2. Restrict network access to the kadmind daemon to trusted administrative hosts only, using firewall rules and network segmentation to limit exposure.
  3. Implement strong authentication and access controls for users permitted to interact with kadmind to reduce the risk of an authenticated attacker exploiting the vulnerability.
  4. Monitor kadmind logs and system behavior for signs of abnormal update sizes or crashes that may indicate exploitation attempts.
  5. Employ intrusion detection/prevention systems (IDS/IPS) with custom signatures to detect anomalous kadmind traffic patterns.
  6. Prepare incident response plans to quickly recover kadmind services in case of a crash, including automated service restarts and failover mechanisms.
  7. Conduct regular security audits and vulnerability assessments focused on authentication infrastructure to identify and remediate similar risks.
  8. Educate system administrators about this vulnerability and the importance of timely patching and access restrictions. These steps go beyond generic advice by focusing on limiting kadmind exposure, monitoring for exploitation indicators, and ensuring rapid recovery to maintain authentication service availability.

Description

In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.

References

Community reviews

Loading reviews…