CVE-2026-20716

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Improper access control for some Intel(R) Processors within Ring 3: User Applications may allow an escalation of privilege. Simple hardware adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

INTEL-SA-01435

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01435.html

Vendor Advisories for CVE-2026-20716(1)

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

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 80× 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.

Showing the most recent 100 of 163 total refreshes for this CVE.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 22:45 UTCGHSA enrichment
  3. 2026-10-04 09:34 UTCGHSA enrichment
  4. 2026-10-03 20:59 UTCEG score recompute
  5. 2026-10-03 20:59 UTCGHSA enrichment
  6. 2026-10-02 22:25 UTCEG score recompute
  7. 2026-10-02 22:25 UTCGHSA enrichment
  8. 2026-10-02 08:42 UTCGHSA enrichment
  9. 2026-10-01 10:52 UTCGHSA enrichment
  10. 2026-09-30 22:17 UTCEG score recompute
  11. 2026-09-30 22:17 UTCGHSA enrichment
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-29 15:21 UTCEPSS rescore
  14. 2026-09-29 05:14 UTCEG score recompute
  15. 2026-09-29 05:14 UTCGHSA enrichment
  16. 2026-09-28 13:51 UTCEPSS rescore
  17. 2026-09-28 02:17 UTCEG score recompute
  18. 2026-09-28 02:17 UTCGHSA enrichment
  19. 2026-09-27 13:47 UTCEPSS rescore
  20. 2026-09-27 10:13 UTCEG score recompute
  21. 2026-09-27 10:13 UTCGHSA enrichment
  22. 2026-09-26 15:58 UTCEPSS rescore
  23. 2026-09-25 03:54 UTCEG score recompute
  24. 2026-09-25 03:54 UTCGHSA enrichment
  25. 2026-09-24 14:03 UTCEPSS rescore
Show 75 more
  1. 2026-09-24 02:25 UTCGHSA enrichment
  2. 2026-09-23 13:50 UTCEG score recompute
  3. 2026-09-23 13:50 UTCGHSA enrichment
  4. 2026-09-23 01:15 UTCEG score recompute
  5. 2026-09-23 01:15 UTCGHSA enrichment
  6. 2026-09-22 12:41 UTCGHSA enrichment
  7. 2026-09-21 23:51 UTCGHSA enrichment
  8. 2026-09-21 10:51 UTCGHSA enrichment
  9. 2026-09-20 19:27 UTCGHSA enrichment
  10. 2026-09-20 05:46 UTCGHSA enrichment
  11. 2026-09-19 17:11 UTCGHSA enrichment
  12. 2026-09-19 03:43 UTCEG score recompute
  13. 2026-09-19 03:43 UTCGHSA enrichment
  14. 2026-09-18 19:27 UTCEPSS rescore
  15. 2026-09-18 15:08 UTCGHSA enrichment
  16. 2026-09-18 02:30 UTCEG score recompute
  17. 2026-09-18 02:30 UTCGHSA enrichment
  18. 2026-09-17 13:55 UTCGHSA enrichment
  19. 2026-09-17 00:32 UTCEG score recompute
  20. 2026-09-17 00:32 UTCGHSA enrichment
  21. 2026-09-16 14:07 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-16 02:07 UTCGHSA enrichment
  24. 2026-09-15 13:23 UTCGHSA enrichment
  25. 2026-09-15 00:26 UTCGHSA enrichment
  26. 2026-09-14 11:48 UTCGHSA enrichment
  27. 2026-09-13 23:14 UTCEG score recompute
  28. 2026-09-13 23:14 UTCGHSA enrichment
  29. 2026-09-13 16:47 UTCEPSS rescore
  30. 2026-09-13 10:39 UTCGHSA enrichment
  31. 2026-09-12 22:03 UTCEG score recompute
  32. 2026-09-12 22:03 UTCGHSA enrichment
  33. 2026-09-12 15:01 UTCEPSS rescore
  34. 2026-09-12 09:27 UTCGHSA enrichment
  35. 2026-09-11 20:52 UTCEG score recompute
  36. 2026-09-11 20:52 UTCGHSA enrichment
  37. 2026-09-11 14:52 UTCEPSS rescore
  38. 2026-09-11 08:07 UTCGHSA enrichment
  39. 2026-09-10 19:32 UTCEG score recompute
  40. 2026-09-10 19:32 UTCGHSA enrichment
  41. 2026-09-10 09:34 UTCEPSS rescore
  42. 2026-09-10 06:50 UTCGHSA enrichment
  43. 2026-09-09 18:15 UTCGHSA enrichment
  44. 2026-09-09 05:40 UTCEG score recompute
  45. 2026-09-09 05:40 UTCGHSA enrichment
  46. 2026-09-08 22:00 UTCEPSS rescore
  47. 2026-09-08 07:15 UTCGHSA enrichment
  48. 2026-09-07 17:00 UTCGHSA enrichment
  49. 2026-09-06 15:48 UTCEG score recompute
  50. 2026-09-06 15:48 UTCGHSA enrichment
  51. 2026-09-06 13:47 UTCEPSS rescore
  52. 2026-09-06 13:47 UTCEPSS rescore
  53. 2026-09-06 03:13 UTCEG score recompute
  54. 2026-09-06 03:13 UTCGHSA enrichment
  55. 2026-09-05 14:38 UTCGHSA enrichment
  56. 2026-09-05 01:43 UTCEG score recompute
  57. 2026-09-05 01:43 UTCGHSA enrichment
  58. 2026-09-04 08:12 UTCEG score recompute
  59. 2026-09-04 08:11 UTCGHSA enrichment
  60. 2026-09-04 05:06 UTCEPSS rescore
  61. 2026-09-03 16:29 UTCGHSA enrichment
  62. 2026-09-03 00:04 UTCGHSA enrichment
  63. 2026-09-02 06:23 UTCGHSA enrichment
  64. 2026-09-01 16:39 UTCEG score recompute
  65. 2026-09-01 16:38 UTCGHSA enrichment
  66. 2026-09-01 13:53 UTCEPSS rescore
  67. 2026-09-01 03:15 UTCEG score recompute
  68. 2026-09-01 03:15 UTCGHSA enrichment
  69. 2026-08-31 14:30 UTCEG score recompute▼ 0.20
  70. 2026-08-31 14:29 UTCGHSA enrichment
  71. 2026-08-31 14:20 UTCNVD updateCVSS v3 → 7
  72. 2026-08-31 11:52 UTCGHSA enrichment
  73. 2026-08-30 23:18 UTCEG score recompute
  74. 2026-08-30 23:18 UTCGHSA enrichment
  75. 2026-08-30 19:17 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-20716?
CVE-2026-20716 is a high vulnerability published on August 11, 2026. Improper access control for some Intel(R) Processors within Ring 3: User Applications may allow an escalation of privilege. Simple hardware adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local…
When was CVE-2026-20716 disclosed?
CVE-2026-20716 was first published on August 11, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20716 actively exploited?
CVE-2026-20716 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20716?
CVE-2026-20716 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-20716?
No fix for CVE-2026-20716 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-20716 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-20716

Explore →

Is Your Infrastructure Affected by CVE-2026-20716?

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

Book a Demo →Browse All CVEs