Skip to main content
VulnerabilityPublished Updated

CVE-2025-64170: sudo-rs · Partial password reveal is possible after timeout

Affects sudo-rsSource GCVE Database

0
Compare
Authoritative record:CVE-2025-64170· Low 3.8

Not known to be exploited · CVSS 3.8 Low : upgrade to 0.2.10 when convenient.

Data as of 13 Nov 2026, 19:07 UTC

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.8
Patch
Available – fixed in 0.2.10
CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade sudo-rs to 0.2.10.

Affected software

ProductAffectedFixed in
crates.iosudo-rsAffected
  • >=0.2.7 <0.2.10
Fixed in
  • 0.2.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in sudo-rs version 0.2.10 that fixes this issue. Users should upgrade to version 0.2.10 or later to prevent partial password disclosure after timeout.

Description

A vulnerability in sudo-rs versions 0.2.7 through 0.2.9 allows partial password input to be revealed on the console if the user delays pressing return until after a password timeout occurs. This can expose partial password information to anyone observing the screen or accessing history files, potentially aiding social engineering or pass-by attacks. The issue is fixed in version 0.2.10.

References

Community reviews

Loading reviews…