CVE-2026-56211

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
Trending — 4 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

A remote code execution vulnerability was found in libaom, the reference AV1 codec implementation. Insufficient bounds validation in the AV1 encoder's SVC (Scalable Video Coding) layer ID control allows an attacker to supply crafted video frame pixels that overlap with internal encoder layer context structures. In fork-based video processing services, an attacker can use this to hijack the cyclic refresh map pointer, brute-force the process base address via a crash oracle, and redirect control flow to achieve arbitrary command execution. Exploitation requires the target service to use libaom with SVC encoding enabled and accept attacker-supplied video frames.

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

Published

June 19, 2026

Last Modified

August 18, 2026

Advisory Details (4)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
generic

Chromium

https://issues.chromium.org/issues/503993985
redhat

2490802 – (CVE-2026-56211) CVE-2026-56211 libaom: libaom: remote code execution via SVC layer context handling with attacker-controlled frames

https://bugzilla.redhat.com/show_bug.cgi?id=2490802
generic

a93ba0ffaa - aom - Git at Google

https://aomedia.googlesource.com/aom/+/a93ba0ffaa
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-56211

Vendor Advisories for CVE-2026-56211(5)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhataom-0:3.14.0-1.el9ai2026-08-06redhat
redhataom-main-3.14.0-0.1.hum12026-06-28redhat

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 rangeFixed inDependents
aom3.10.0-1 ... 3.9.1-1~exp1 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
aom3.12.1-13.12.1-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
aom3.12.1-1, 3.13.1-1, 3.13.1-1~exp1, 3.13.1-23.14.1-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 39× in last 7d / 172× 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 301 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56211?
CVE-2026-56211 is a high vulnerability published on June 19, 2026. A remote code execution vulnerability was found in libaom, the reference AV1 codec implementation. Insufficient bounds validation in the AV1 encoder's SVC (Scalable Video Coding) layer ID control allows an attacker to supply crafted video frame pixels that overlap with internal encoder layer…
When was CVE-2026-56211 disclosed?
CVE-2026-56211 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56211 actively exploited?
CVE-2026-56211 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 62.3% of all scored CVEs.
What is the CVSS score of CVE-2026-56211?
CVE-2026-56211 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-56211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56211, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56211?

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

Start Free Scan →Browse All CVEs