CVE-2026-25506

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 10, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 12, 2026
Patch available. Sources: github, github_commit, github_release.
Web pageMentions a patch (unverified)

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

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

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
Web page

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 advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / 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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
munge0.5.14-4
  • every version up to 0.5.14-4+deb11u1: fixed in 0.5.14-4+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
munge0.5.15-2
  • every version up to 0.5.15-2+deb12u1: fixed in 0.5.15-2+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
munge0.5.16-1
  • every version up to 0.5.16-1.1~deb13u1: fixed in 0.5.16-1.1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
munge0.5.16-1, 0.5.16-1.1~deb13u1
  • every version up to 0.5.16-1.1: fixed in 0.5.16-1.1
—

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 12× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 192 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25506?
CVE-2026-25506 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-25506 published?
The CVE record for CVE-2026-25506 was published on February 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-25506 actively exploited?
CVE-2026-25506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25506?
CVE-2026-25506 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-25506?
A fix for CVE-2026-25506 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25506 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs