CVE-2026-21069

HIGHNVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory published 2026-08-10. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

Incorrect conversion between numeric types in VC1 codec in libsavsvc.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory.

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

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (1)

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

Samsung Mobile Security

https://security.samsungmobile.com/securityUpdate.smsb?year=2026&month=08

Vendor Advisories for CVE-2026-21069(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 26× in last 7d / 42× 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-21 03:58 UTCEG score recompute
  2. 2026-08-21 03:58 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:27 UTCGHSA enrichment
  5. 2026-08-20 04:57 UTCEG score recompute
  6. 2026-08-20 04:57 UTCGHSA enrichment
  7. 2026-08-19 17:26 UTCEG score recompute▲ 2.70
  8. 2026-08-19 17:26 UTCGHSA enrichment
  9. 2026-08-19 17:16 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-19 16:19 UTCGHSA enrichment
  12. 2026-08-18 15:34 UTCEG score recompute
  13. 2026-08-18 15:33 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 23:02 UTCEG score recompute
  16. 2026-08-17 23:01 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 22:22 UTCEG score recompute
  19. 2026-08-16 22:22 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 21:43 UTCEG score recompute
  23. 2026-08-15 21:43 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 21:03 UTCEG score recompute
Show 17 more
  1. 2026-08-14 21:03 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 20:24 UTCGHSA enrichment
  4. 2026-08-12 19:44 UTCEG score recompute
  5. 2026-08-12 19:44 UTCGHSA enrichment
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-11 19:05 UTCEG score recompute
  8. 2026-08-11 19:05 UTCGHSA enrichment
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-10 18:25 UTCEG score recompute
  12. 2026-08-10 18:25 UTCGHSA enrichment
  13. 2026-08-10 17:55 UTCEG score recompute
  14. 2026-08-10 17:55 UTCGHSA enrichment
  15. 2026-08-10 09:20 UTCEG score recompute
  16. 2026-08-10 08:16 UTCEG score recompute
  17. 2026-08-10 08:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-21069?
CVE-2026-21069 is a high vulnerability published on August 10, 2026. Incorrect conversion between numeric types in VC1 codec in libsavsvc.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory.
When was CVE-2026-21069 disclosed?
CVE-2026-21069 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21069 actively exploited?
CVE-2026-21069 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-21069?
CVE-2026-21069 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-21069?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21069, 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-21069

Explore →

Is Your Infrastructure Affected by CVE-2026-21069?

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

Start Free Scan →Browse All CVEs