CVE-2025-64517

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

Score 4.4 from GitHub Security Advisory (severity: MODERATE) published 2025-11-13. A secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-150364 (ENISA EUVD) · GHSA-q428-6v73-fc4q (GitHub Security Advisories)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

sudo-rs is a memory safe implementation of sudo and su written in Rust. With Defaults targetpw (or Defaults rootpw) enabled, the password of the target account (or root account) instead of the invoking user is used for authentication. sudo-rs starting in version 0.2.5 and prior to version 0.2.10 incorrectly recorded the invoking user’s UID instead of the authenticated-as user's UID in the authentication timestamp. Any later sudo invocation on the same terminal while the timestamp was still valid would use that timestamp, potentially bypassing new authentication even if the policy would have required it. A highly-privileged user (able to run commands as other users, or as root, through sudo) who knows one password of an account they are allowed to run commands as, would be able to run commands as any other account the policy permits them to run commands for, even if they don't know the password for those accounts. A common instance of this would be that a user can still use their own password to run commands as root (the default behaviour of sudo), effectively negating the intended behaviour of the targetpw or rootpw options. Version 0.2.10 contains a patch for the issue. Versions prior to 0.2.5 are not affected, since they do not offer Defaults targetpw or Defaults rootpw.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

November 12, 2025

Last Modified

October 18, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustsudo-rs @ 0.2.10 (fixes >= 0.2.5, < 0.2.10)—ghsa

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

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
sudo-rs—
  • 0.2.5 up to 0.2.10: fixed in 0.2.10
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-sudo-rs0.2.5-5
  • every version up to 0.2.5-5+deb13u1: fixed in 0.2.5-5+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-sudo-rs0.2.5-5, 0.2.9-1
  • every version up to 0.2.10-1: fixed in 0.2.10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 217 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 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

4 shown

Debian:13:rust-sudo-rs · crates.io:sudo-rs

Frequently asked(5)

What is CVE-2025-64517?
CVE-2025-64517 is a medium-severity vulnerability; its CVE record was published on November 12, 2025. sudo-rs is a memory safe implementation of sudo and su written in Rust. With Defaults targetpw (or Defaults rootpw) enabled, the password of the target account (or root account) instead of the invoking user is used for authentication. sudo-rs starting in version 0.2.5 and prior to version 0.2.10…
When was the CVE record for CVE-2025-64517 published?
The CVE record for CVE-2025-64517 was published on November 12, 2025. 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 October 18, 2026; the record at its source may have been updated since.
Is CVE-2025-64517 actively exploited?
CVE-2025-64517 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-64517?
CVE-2025-64517 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-64517?
A fix for CVE-2025-64517 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-64517

Explore →

Is Your Infrastructure Affected by CVE-2025-64517?

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

Book a Demo →Browse All CVEs