CVE-2026-20468

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreHIGH confidence

Score 6.0 from GitHub Security Advisory published 2026-08-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

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

In apusys, there is a possible escalation of privilege due to a confused deputy. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: AUTO00833804; Issue ID: MSV-6741.

CVSS v3
6.0
EG Score
6.0(high)
EG Risk
27(Track)
EG Risk 27/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 computed
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated Aug 3, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

August 2026 MediaTek Security Bulletin

https://www.mediatek.com/product-security-bulletin/August-2026

Vendor Advisories for CVE-2026-20468(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 19× in last 7d / 59× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 16:50 UTCGHSA enrichment
  3. 2026-08-19 19:01 UTCEG score recompute
  4. 2026-08-19 19:01 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 19:20 UTCEG score recompute
  7. 2026-08-18 19:20 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 21:36 UTCEG score recompute
  10. 2026-08-17 21:36 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 23:54 UTCEG score recompute
  13. 2026-08-16 23:54 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-16 02:12 UTCGHSA enrichment
  17. 2026-08-15 04:30 UTCEG score recompute
  18. 2026-08-15 04:30 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 06:47 UTCEG score recompute
  21. 2026-08-14 06:47 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 09:04 UTCEG score recompute
  24. 2026-08-13 09:04 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 34 more
  1. 2026-08-12 11:21 UTCEG score recompute
  2. 2026-08-12 11:21 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 13:38 UTCEG score recompute
  5. 2026-08-11 13:38 UTCGHSA enrichment
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 15:55 UTCGHSA enrichment
  8. 2026-08-09 17:59 UTCEG score recompute
  9. 2026-08-09 17:59 UTCGHSA enrichment
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 20:17 UTCEG score recompute
  12. 2026-08-08 20:17 UTCGHSA enrichment
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 22:35 UTCEG score recompute
  15. 2026-08-07 22:35 UTCGHSA enrichment
  16. 2026-08-07 00:52 UTCEG score recompute
  17. 2026-08-07 00:52 UTCGHSA enrichment
  18. 2026-08-06 13:46 UTCEPSS rescore
  19. 2026-08-06 03:10 UTCEG score recompute
  20. 2026-08-06 03:10 UTCGHSA enrichment
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-05 05:28 UTCGHSA enrichment
  23. 2026-08-05 04:42 UTCGHSA enrichment
  24. 2026-08-04 18:03 UTCEG score recompute
  25. 2026-08-04 18:03 UTCGHSA enrichment
  26. 2026-08-04 15:10 UTCEPSS rescore
  27. 2026-08-04 10:38 UTCEPSS rescore
  28. 2026-08-03 20:20 UTCGHSA enrichment
  29. 2026-08-03 20:13 UTCEG score recompute▲ 6.00
  30. 2026-08-03 20:13 UTCGHSA enrichment
  31. 2026-08-03 20:13 UTCMITRE cvelistV5CVSS v3 → 6 · severity → MEDIUM
  32. 2026-08-03 03:23 UTCNVD update
  33. 2026-08-03 02:44 UTCEG score recompute
  34. 2026-08-03 02:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20468?
CVE-2026-20468 is a medium vulnerability published on August 3, 2026. In apusys, there is a possible escalation of privilege due to a confused deputy. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: AUTO00833804; Issue ID: MSV-6741.
When was CVE-2026-20468 disclosed?
CVE-2026-20468 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20468 actively exploited?
CVE-2026-20468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-20468?
CVE-2026-20468 has a CVSS v3.1 base score of 6.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-20468?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20468, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-20468

Explore →

Is Your Infrastructure Affected by CVE-2026-20468?

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

Start Free Scan →Browse All CVEs