CVE-2026-56211

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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(high)
EPSS
31.9%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 6, 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(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 July 6, 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 31.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56211?
CVE-2026-56211 has a CVSS v3 base score of 7.1 (NVD).
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

Explore the affected products and dependency analysis for 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