HomeDescription
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.
PUBLISHED Reserved 2026-06-19 | Published 2026-06-19 | Updated 2026-07-06 | Assigner redhat
HIGH: 7.1CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H
Problem types
Out-of-bounds Write
Product status
Default status
affected
3.14.0-0.1.hum1 (rpm) before *
unaffected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
unaffected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Timeline
| 2026-06-19: | Reported to Red Hat. |
| 2026-06-19: | Made public. |
Credits
Red Hat would like to thank The FuzzAnything Team (FuzzAnything) for reporting this issue.
References
access.redhat.com/security/cve/CVE-2026-56211 vdb-entry
bugzilla.redhat.com/show_bug.cgi?id=2490802 (RHBZ#2490802) issue-tracking
security.access.redhat.com/...2/vex/2026/cve-2026-56211.json
access.redhat.com/errata/RHSA-2026:30814 vendor-advisory
access.redhat.com/errata/RHSA-2026:30814 (RHSA-2026:30814) vendor-advisory
access.redhat.com/security/cve/CVE-2026-56211 vdb-entry
aomedia.googlesource.com/aom/+/a93ba0ffaa
bugzilla.redhat.com/show_bug.cgi?id=2490802 (RHBZ#2490802) issue-tracking
issues.chromium.org/issues/503993985
cve.org (CVE-2026-56211)
nvd.nist.gov (CVE-2026-56211)
Download JSON