CVE-2025-64517VulnerabilityPublished 12 Nov 2025Updated 19 Nov 2025

Rust sudo rs: With Defaults targetpw (or Defaults rootpw) enabled, the password of the target account (or root

Affects rust-sudo-rsSource GCVE Database

Compare

Authoritative record:CVE-2025-64517· Medium 4.4

Not known to be exploited · CVSS 4.4 Medium : upgrade to 0.2.8-1ubuntu5.2 when convenient.

Data as of 13 Nov 2026, 20:32 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.2.8-1ubuntu5.2

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Ubuntu rust-sudo-rs package to 0.2.8-1ubuntu5.2.

Patches and advisories

ubuntu.com/security/notices/USN-7867-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 25.10rust-sudo-rs`pkg:deb/ubuntu/rust-sudo-rs?arch=source&distro=questing`Other threats	Affected <0.2.8-1ubuntu5.2	Fixed in 0.2.8-1ubuntu5.2

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

AI-suggested

Update sudo-rs to version 0.2.8-1ubuntu5.2 or later, which contains the official fix for this vulnerability. A standard system update on affected Ubuntu releases will apply the necessary patch. No other mitigation is required as the issue is resolved in the fixed version.

Description

A vulnerability in sudo-rs versions prior to 0.2.8-1ubuntu5.2 allows bypassing authentication when the Defaults targetpw or rootpw options are enabled. The issue arises because sudo-rs incorrectly records the invoking user's UID instead of the authenticated user's UID in the authentication timestamp, enabling a privileged user to run commands as other permitted accounts without knowing their passwords. This flaw is patched in version 0.2.8-1ubuntu5.2.

Impact

An attacker with privileges to run commands as other users via sudo-rs and knowledge of one account's password can bypass authentication for other accounts allowed by policy, potentially escalating privileges or executing commands without proper authentication. This undermines the security controls intended by the targetpw or rootpw sudo options. There is no confidentiality or availability impact reported, but integrity is affected due to unauthorized command execution.

References

Community reviews

Loading reviews…