basicsecurity.net
Proof, not just disclosure.
Threats / Sudo / CVE-2025-32463
CVE-2025-32463 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-293EPSS 0.48008 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
4 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.48008 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Sudo, Sudo. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-829 Inclusion of Untrusted Functionality — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.