Skip to content
major vulnerability· requires attention

Sudo is a ubiquitous system utility; this bypass enables policy evasion and potential local privilege escalation across many Linux/Unix environments.

Systems

CVE-2026-82474

8.5
High
EPSS 0.13%Patch availableSep 1, 2026

Sudo intercept mode bypass via execveat lets permitted users run denied programs.

common questions

Is CVE-2026-82474 being exploited?

Not confirmed. CVE-2026-82474 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-82474?

CVE-2026-82474 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-82474?

Yes. A fix has been recorded for CVE-2026-82474. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-82474 affect?

CVE-2026-82474 affects sudo <= 1.9.17p2, systems using ptrace-based intercept mode. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82474?

Upgrade sudo to the patched release (>1.9.17p2) or apply vendor patch immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
sudo <= 1.9.17p2systems using ptrace-based intercept mode
impact

Local policy bypass: allowed sudo users can invoke execveat/fexecve to run denied programs, enabling unauthorized command execution or privilege escalation.

action required

Immediate action required

affected versions
sudo-project sudo
  • affected<= 1.9.17p2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free