Threats / Sudo / CVE-2025-32463
CVE-2025-32463
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Sudo vulnerability
Sudo contains an inclusion of untrusted functionality that allows local attackers to execute arbitrary commands as root via the -R (--chroot) option, bypassing sudoers file restrictions.
Verdict
Today item — known-exploited.
A local attacker can exploit Sudo's chroot option to gain unauthorized root command execution, circumventing access controls. This vulnerability is actively exploited in the wild and poses significant privilege escalation risk on affected systems.
CISA KEV Yes · 2025-09-295EPSS 0.54935 (verify live)6Exploit Weaponized · public PoC7CVSS 9.33CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-09-29).
Probability (EPSS)
EPSS 0.54935 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.3 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Sudo, Sudo. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-829 Inclusion of Untrusted Functionality — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 91 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain local system access as an unprivileged user.
Business
An attacker establishes initial foothold on the host system.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I invoke sudo with the -R flag to execute arbitrary commands as root outside normal sudoers restrictions.
Business
Access controls enforced by sudoers configuration are bypassed, enabling unauthorized privilege escalation.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute malicious commands with root privileges to modify system files, install backdoors, or exfiltrate data.
Business
Complete system compromise occurs, allowing data theft, lateral movement, and persistent unauthorized access.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05