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 — 3 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
33.8%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
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

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 12× in last 7d / 123× 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 130 total refreshes for this CVE.

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

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 22, 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 33.8% 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.