CVE-2026-25506

HIGHNVD 7.87.7▼
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.7(medium)
EPSS
22.2%
KEV
Not listed

Published

February 10, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
generic Patch Available

[SECURITY] [DLA 4477-1] munge security update

https://lists.debian.org/debian-lts-announce/2026/02/msg00015.html
generic

oss-security - Re: CVE-2026-25506: MUNGE 0.5-0.5.17 buffer overflow allowing key leakage

http://www.openwall.com/lists/oss-security/2026/02/17/6
generic

oss-security - CVE-2026-25506: MUNGE 0.5-0.5.17 buffer overflow allowing key leakage

http://www.openwall.com/lists/oss-security/2026/02/10/3
github Patch Available🟡 PoC Available

Buffer overflow in message unpacking allows key leakage and credential forgery · Advisory · dun/munge · GitHub

https://github.com/dun/munge/security/advisories/GHSA-r9cr-jf4v-75gh
github_release Patch Available

munge-0.5.18

Patch available: dun/munge munge-0.5.18

https://github.com/dun/munge/releases/tag/munge-0.5.18
github_commit Patch Available

commit bf40cc27c4ce (dun/munge)

Patch available: dun/munge munge-0.5.18 (contains commit bf40cc27c4ce)

https://github.com/dun/munge/commit/bf40cc27c4ce8451d4b062c9de0b67ec40894812

Vendor Advisories for CVE-2026-25506(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumunge (0.5.13-1ubuntu0.1~esm1) @ bionic2026-06-12ubuntu
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatmunge-0:0.5.13-3.el8_102026-02-23redhat
redhatmunge-0:0.5.13-14.el9_72026-02-23redhat
redhatmunge-0:0.5.15-11.el10_12026-02-23redhat
redhatmunge-0:0.5.13-2.el8_6.12026-02-19redhat
redhatmunge-0:0.5.13-1.el8_2.12026-02-19redhat
redhatmunge-0:0.5.13-2.el8_4.12026-02-19redhat
redhatmunge-0:0.5.13-2.el8_8.12026-02-19redhat
redhatmunge-0:0.5.13-13.el9_4.12026-02-18redhat
redhatmunge-0:0.5.13-13.el9_6.12026-02-18redhat
redhatmunge-0:0.5.15-10.el10_0.12026-02-18redhat
redhatmunge-0:0.5.13-13.el9_0.12026-02-18redhat
redhatmunge-0:0.5.13-13.el9_2.12026-02-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 7.8
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 7.7
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 70 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-30 04:31 UTCNVD updateCVSS v3 → 7.8
  4. 2026-06-29 14:32 UTCOSV refresh
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 14:07 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-17 17:53 UTCEPSS rescore
  27. 2026-06-17 17:53 UTCEPSS rescore
  28. 2026-06-16 17:52 UTCEPSS rescore
  29. 2026-06-15 17:48 UTCEPSS rescore
  30. 2026-06-14 23:18 UTCEPSS rescore
  31. 2026-06-13 23:00 UTCEPSS rescore
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 04:38 UTCEG score recompute
  35. 2026-06-12 04:38 UTCVendor advisory
  36. 2026-06-11 14:00 UTCEPSS rescore
  37. 2026-06-10 22:18 UTCEPSS rescore
  38. 2026-06-10 22:18 UTCEPSS rescore
  39. 2026-06-10 13:22 UTCEPSS rescore
  40. 2026-06-10 03:13 UTCEG score recompute
  41. 2026-06-10 03:13 UTCVendor advisory
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 07:05 UTCEG score recompute
  45. 2026-06-08 07:05 UTCVendor advisory
  46. 2026-06-07 19:37 UTCEG score recompute
  47. 2026-06-07 19:37 UTCVendor advisory
  48. 2026-06-07 15:25 UTCEPSS rescore
  49. 2026-06-07 15:25 UTCEPSS rescore
  50. 2026-06-07 15:25 UTCEPSS rescore
  51. 2026-06-06 13:47 UTCEPSS rescore
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 22:47 UTCEPSS rescore
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-02 20:13 UTCEPSS rescore
  60. 2026-06-02 20:13 UTCEPSS rescore
  61. 2026-06-01 13:51 UTCEPSS rescore
  62. 2026-06-01 13:51 UTCEPSS rescore
  63. 2026-05-31 22:30 UTCEPSS rescore
  64. 2026-05-31 22:30 UTCEPSS rescore
  65. 2026-05-31 00:16 UTCEPSS rescore
  66. 2026-05-31 00:16 UTCEPSS rescore
  67. 2026-05-29 14:09 UTCEG score recompute
  68. 2026-05-29 14:09 UTCVendor advisory
  69. 2026-05-29 13:44 UTCEPSS rescore
  70. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25506?
CVE-2026-25506 is a high vulnerability published on February 10, 2026. 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…
When was CVE-2026-25506 disclosed?
CVE-2026-25506 was first published in the National Vulnerability Database on February 10, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25506 actively exploited?
CVE-2026-25506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25506?
CVE-2026-25506 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2026-25506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25506, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-25506

Explore →

Is Your Infrastructure Affected by CVE-2026-25506?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs