# CVE-2026-25506: MUNGE has a buffer overflow in message unpacking allows key leakage and credential forgery > Local attackers can exploit a buffer overflow in MUNGE to leak keys and forge credentials, enabling impersonation of any user including root. - **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Feb 2026 - **Updated:** 15 Jul 2026 - **Also known as:** ALSA-2026:3032, ALSA-2026:3033, ALSA-2026:3034, AZL-77444, AZL-77451, CLSA-2026-1772571803, CLSA-2026-1772572505, DEBIAN-CVE-2026-25506, DLA-4477-1, DSA-6129-1, GHSA-r9cr-jf4v-75gh, OESA-2026-1348, RHSA-2026:2918, RHSA-2026:2923, RHSA-2026:2934, RHSA-2026:2949, RHSA-2026:2954, RHSA-2026:3010, RHSA-2026:3011, RHSA-2026:3012, RHSA-2026:3013, RHSA-2026:3032, RHSA-2026:3033, RHSA-2026:3034, RLSA-2026:3032, RLSA-2026:3033, RLSA-2026:3034, SUSE-SU-2026:0448-1, SUSE-SU-2026:0450-1, SUSE-SU-2026:0451-1, SUSE-SU-2026:0484-1, UBUNTU-CVE-2026-25506, USN-8040-1, openSUSE-SU-2026:10178-1 ## What is CVE-2026-25506? CVE-2026-25506 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description MUNGE is an authentication service for creating and validating user credentials. From 0.5 to 0.5.17, local attacker can exploit a buffer overflow vulnerability in munged (the MUNGE authentication daemon) to leak cryptographic key material from process memory. With the leaked key material, the attacker could forge arbitrary MUNGE credentials to impersonate any user (including root) to services that rely on MUNGE for authentication. The vulnerability allows a buffer overflow by sending a crafted message with an oversized address length field, corrupting munged's internal state and enabling extraction of the MAC subkey used for credential verification. This vulnerability is fixed in 0.5.18. Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2026-25506? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `munge` | AlmaLinux:10 | All versions | 0.5.15-11.el10_1 | | `munge-devel` | AlmaLinux:10 | All versions | 0.5.15-11.el10_1 | | `munge-libs` | AlmaLinux:10 | All versions | 0.5.15-11.el10_1 | | `munge` | AlmaLinux:8 | All versions | 0.5.13-3.el8_10 | | `munge-devel` | AlmaLinux:8 | All versions | 0.5.13-3.el8_10 | | `munge-libs` | AlmaLinux:8 | All versions | 0.5.13-3.el8_10 | | `munge` | AlmaLinux:9 | All versions | 0.5.13-14.el9_7 | | `munge-devel` | AlmaLinux:9 | All versions | 0.5.13-14.el9_7 | | `munge-libs` | AlmaLinux:9 | All versions | 0.5.13-14.el9_7 | | `munge` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge-libs` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:0.5.15-11.el10_1 | | `munge` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.5.13-3.el8_10 | | `munge-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.5.13-3.el8_10 | | `munge-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.5.13-3.el8_10 | | `munge-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.5.13-3.el8_10 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.5.13-3.el8_10 | | `munge-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.5.13-3.el8_10 | | `munge-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.5.13-3.el8_10 | | `munge-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.5.13-3.el8_10 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.5.13-3.el8_10 | | `munge` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.5.13-14.el9_7 | | `munge-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.5.13-14.el9_7 | | `munge-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.5.13-14.el9_7 | | `munge-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.5.13-14.el9_7 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.5.13-14.el9_7 | | `munge-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.5.13-14.el9_7 | | `munge-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.5.13-14.el9_7 | | `munge-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.5.13-14.el9_7 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.5.13-14.el9_7 | | `munge` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge-libs` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge-libs-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.5.15-10.el10_0.1 | | `munge` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:0.5.13-1.el8_2.1 | Products: Debian Debian Linux, Opensuse Munge. ## How do I fix CVE-2026-25506? Upgrade to a fixed version. ## Is CVE-2026-25506 being exploited? There is no known exploitation of CVE-2026-25506 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25506 and fix it if it is affected. What it is: CVE-2026-25506 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-25506 in the wild and no public exploit code. Affected product: Debian Debian Linux. 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-2026-25506/ (Markdown: https://insights.sbomify.com/CVE-2026-25506/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25506 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25506 - OSV: https://osv.dev/vulnerability/CVE-2026-25506 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25506/ Summaries are generated and may contain mistakes; the official description above is the record.