# CVE-2025-24528: Integer overflow in Kerberos 5 > An authenticated attacker can cause a kadmind daemon crash via integer overflow in Kerberos 5 when incremental propagation is enabled. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Jan 2026 - **Updated:** 16 Jan 2026 - **Also known as:** ALSA-2025:2722, ALSA-2025:7067, AZL-74852, AZL-74862, BELL-CVE-2025-24528, CLSA-2025-1742662173, CLSA-2025-1742723370, CLSA-2025-1755791979, CLSA-2025-1759506149, DEBIAN-CVE-2025-24528, DLA-4065-1, ECHO-84be-2f2e-7407, GHSA-wrjh-fhfj-xhfm, MGASA-2025-0072, OESA-2025-1135, RHSA-2025:1352, RHSA-2025:2722, RHSA-2025:7067, RLSA-2025:2722, RLSA-2025:7067, SUSE-SU-2025:0304-1, SUSE-SU-2025:0343-1, SUSE-SU-2025:0351-1, SUSE-SU-2025:0401-1, SUSE-SU-2025:0822-1, SUSE-SU-2025:20153-1, SUSE-SU-2025:20303-1, UBUNTU-CVE-2025-24528, openSUSE-SU-2025:14736-1 ## What is CVE-2025-24528? CVE-2025-24528 is a high-severity vulnerability in MIT Kerberos 5, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2025-24528? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `krb5-devel` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-libs` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-pkinit` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-server` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-server-ldap` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-workstation` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `libkadm5` | AlmaLinux:8 | All versions | 1.18.2-31.el8_10 | | `krb5-devel` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5-libs` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5-pkinit` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5-server` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5-server-ldap` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5-workstation` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `libkadm5` | AlmaLinux:9 | All versions | 1.21.1-6.el9 | | `krb5` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-pkinit` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-pkinit-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-server` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-server-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-server-ldap` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-server-ldap-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-workstation` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-workstation-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `libkadm5` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `libkadm5-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.18.2-31.el8_10 | | `krb5-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-pkinit-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-server-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-server-ldap-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `krb5-workstation-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | | `libkadm5-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.21.1-6.el9 | ## How do I fix CVE-2025-24528? Upgrade to a fixed version. ## Is CVE-2025-24528 being exploited? There is no known exploitation of CVE-2025-24528 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-24528 and fix it if it is affected. What it is: CVE-2025-24528 is a high-severity vulnerability in MIT Kerberos 5, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-24528 in the wild and no public exploit code. Affected product: MIT Kerberos 5. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-24528/ (Markdown: https://insights.sbomify.com/CVE-2025-24528/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24528 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24528 - OSV: https://osv.dev/vulnerability/CVE-2025-24528 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-24528/ Summaries are generated and may contain mistakes; the official description above is the record.