Sudo through 1.9.17p2 fails to apply intercept policy checks to the execveat system call in ptrace-based intercept mode. Users permitted to run specific commands can execute denied programs by calling execveat directly or through fexecve, bypassing policy enforcement and logging.
CVE-2026-82474
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-29. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (4)
Auto-updated Aug 29, 2026Sudo through 1.9.17p2 Intercept Policy Bypass via execveat | Advisories | VulnCheck
https://www.vulncheck.com/advisories/sudo-through-1.9-17p2-intercept-policy-bypass-via-execveatGitHub - sudo-project/sudo: Utility to execute a command as another user · GitHub
https://github.com/sudo-project/sudosudo/src/exec_ptrace.c at v1.9.17p2 · sudo-project/sudo · GitHub
https://github.com/sudo-project/sudo/blob/v1.9.17p2/src/exec_ptrace.ccommit 71fbe42dcd5a (sudo-project/sudo)
Fix landed in sudo-project/sudo commit 71fbe42dcd5a — awaiting tagged release
https://github.com/sudo-project/sudo/commit/71fbe42dcd5a1c8f799540583a2dfb2ae6221edfVendor Advisories for CVE-2026-82474(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 06:31 UTCEG score recompute
- 2026-08-30 06:31 UTCGHSA enrichment
- 2026-08-29 17:28 UTCEG score recompute
- 2026-08-29 16:41 UTCEG score recompute
- 2026-08-29 16:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS p91CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS p100CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8CRITICAL
- CVE-2020-10887EG 9.8EPSS p90CRITICAL
- CVE-2017-3197EG 9.8EPSS p96CRITICAL
- CVE-2018-9318EG 9.8EPSS p95CRITICAL
- CVE-2018-9311EG 9.8EPSS p95CRITICAL
- CVE-2017-8864EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS p100CRITICAL
Frequently asked(4)
What is CVE-2026-82474?
When was CVE-2026-82474 disclosed?
What is the CVSS score of CVE-2026-82474?
How do I remediate CVE-2026-82474?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82474
Is Your Infrastructure Affected by CVE-2026-82474?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.