CVE-2026-82474

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 29, 2026

Last Modified

September 10, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
Patch available. Sources: github_commit.
Web page

Sudo 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-execveat
Web page

GitHub - sudo-project/sudo: Utility to execute a command as another user · GitHub

https://github.com/sudo-project/sudo
Web page

sudo/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.c
GitHub commit

commit 71fbe42dcd5a (sudo-project/sudo)

Fix landed in sudo-project/sudo commit 71fbe42dcd5a — awaiting tagged release

https://github.com/sudo-project/sudo/commit/71fbe42dcd5a1c8f799540583a2dfb2ae6221edf

Vendor Advisories for CVE-2026-82474(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusudo (1.9.17p2-1ubuntu3.1) @ resolute2026-10-10ubuntu
redhatrhui5/rhua-rhel9:17902420042026-09-24redhat
redhatsudo-0:1.9.15-8.p5.el10_0.42026-09-24redhat
redhatsudo-0:1.9.17p2-3.el9_8.12026-09-21redhat
redhatsudo-0:1.9.17-10.p2.el10_2.62026-09-17redhat
redhatsudo-main-1.9.17-16.p2.1.hum12026-09-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sudo1.9.13p3-1 ... 1.9.17p2-9 (34 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sudo1.9.16p2-3 ... 1.9.17p2-9 (14 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sudo1.9.16p2-3 ... 1.9.17p2-9 (12 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 146× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-13 06:03 UTCEG score recompute
  3. 2026-10-13 06:03 UTCVendor advisory
  4. 2026-10-13 06:03 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-12 14:55 UTCEG score recompute
  7. 2026-10-11 19:19 UTCEG score recompute
  8. 2026-10-11 16:36 UTCEG score recompute
  9. 2026-10-11 13:54 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-10 13:52 UTCVendor advisory
  13. 2026-10-10 13:51 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-10 00:45 UTCEG score recompute
  15. 2026-10-10 00:45 UTCVendor advisory
  16. 2026-10-10 00:45 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-09 02:34 UTCEG score recompute
  19. 2026-10-09 02:34 UTCVendor advisory
  20. 2026-10-09 02:33 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-08 00:45 UTCEG score recompute
  23. 2026-10-08 00:45 UTCVendor advisory
  24. 2026-10-08 00:45 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 75 more
  1. 2026-10-07 02:54 UTCEG score recompute
  2. 2026-10-07 02:54 UTCVendor advisory
  3. 2026-10-07 02:54 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-06 13:50 UTCVendor advisory
  6. 2026-10-06 13:50 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-06 00:47 UTCEG score recompute
  8. 2026-10-06 00:47 UTCVendor advisory
  9. 2026-10-06 00:47 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-05 08:39 UTCEG score recompute
  12. 2026-10-05 08:39 UTCVendor advisory
  13. 2026-10-05 08:39 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-04 19:35 UTCVendor advisory
  16. 2026-10-04 19:35 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-04 04:01 UTCVendor advisory
  18. 2026-10-04 04:01 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-03 14:56 UTCEG score recompute
  20. 2026-10-03 14:56 UTCVendor advisory
  21. 2026-10-03 14:56 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-03 01:53 UTCEG score recompute
  24. 2026-10-03 01:53 UTCVendor advisory
  25. 2026-10-03 01:53 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-10-02 12:49 UTCVendor advisory
  28. 2026-10-02 12:49 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-10-01 22:31 UTCEG score recompute
  30. 2026-10-01 22:31 UTCVendor advisory
  31. 2026-10-01 22:31 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-10-01 08:51 UTCVendor advisory
  34. 2026-10-01 08:51 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-30 19:47 UTCEG score recompute
  36. 2026-09-30 19:47 UTCVendor advisory
  37. 2026-09-30 19:47 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-30 03:48 UTCEG score recompute
  40. 2026-09-30 03:48 UTCVendor advisory
  41. 2026-09-30 03:48 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-09-29 14:32 UTCVendor advisory
  43. 2026-09-29 14:31 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-09-29 01:22 UTCEG score recompute
  45. 2026-09-29 01:22 UTCVendor advisory
  46. 2026-09-29 01:22 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-28 12:19 UTCVendor advisory
  49. 2026-09-28 12:19 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-27 23:15 UTCEG score recompute
  51. 2026-09-27 23:15 UTCVendor advisory
  52. 2026-09-27 23:15 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-09-27 10:11 UTCVendor advisory
  55. 2026-09-27 10:11 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-09-26 21:08 UTCEG score recompute
  57. 2026-09-26 21:08 UTCVendor advisory
  58. 2026-09-26 21:08 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-09-26 08:01 UTCEG score recompute
  61. 2026-09-26 08:01 UTCVendor advisory
  62. 2026-09-26 08:01 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-25 13:15 UTCVendor advisory
  64. 2026-09-25 13:15 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-25 00:12 UTCEG score recompute
  66. 2026-09-25 00:12 UTCVendor advisory
  67. 2026-09-25 00:12 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-09-24 10:40 UTCVendor advisory
  70. 2026-09-24 10:40 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-09-23 21:32 UTCVendor advisory
  72. 2026-09-23 21:32 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-09-23 08:29 UTCVendor advisory
  74. 2026-09-23 08:29 UTCGHSA enrichmentGHSA-36m7-65w5-jm6c · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-22 19:26 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-82474?
CVE-2026-82474 is a high-severity vulnerability; its CVE record was published on August 29, 2026. 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.
When was CVE-2026-82474 made public?
CVE-2026-82474 was made public on March 20, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 29, 2026. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-82474 actively exploited?
CVE-2026-82474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82474?
CVE-2026-82474 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82474?
A fix for CVE-2026-82474 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82474 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82474

Explore →

Is Your Infrastructure Affected by CVE-2026-82474?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs