CVE-2026-56211 — Libaom: libaom: remote code execution via svc layer context handling with attacker-controlled frames
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.9% (30-day exploitation probability)+9
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Red Hat Ai Inference Server, Red Hat Hardened Images, Red Hat Red Hat AI Inference Server 3.2…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Red Hat | Ai Inference Server | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Hardened Images | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat AI Inference Server 3.2 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat AI Inference Server 3.3 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux 10 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux AI 3.3 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux AI 3.3 for RHEL 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux AI 3.4 for RHEL 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux AI 3.5 for RHEL 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat OpenShift AI (RHOAI) | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat OpenShift AI 3.3 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat OpenShift AI 3.4 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat OpenShift AI 3.5 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 1.6 | 5.5 | secalert@redhat.com via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | 1.6 | 5.5 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | redhat via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H (score shown at the top: secalert@redhat.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.88%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · red hat/red hat enterprise linux ai 3.3 for rhel 9, red hat/red hat enterprise linux ai 3.4 for rhel 9, red hat/red hat
- SSVC assessment updated
- Record published
- CVSS changed · 7.1
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
52 on the record
- access.redhat.com/errata/RHSA-2026:71401
- access.redhat.com/errata/RHSA-2026:71395
- access.redhat.com/errata/RHSA-2026:74771
- bugzilla.redhat.com/show_bug.cgi
- access.redhat.com/errata/RHSA-2026:69934
- access.redhat.com/errata/RHSA-2026:68710
- access.redhat.com/errata/RHSA-2026:68697
- access.redhat.com/errata/RHSA-2026:68634
- access.redhat.com/errata/RHSA-2026:68637
- access.redhat.com/errata/RHSA-2026:76042
- access.redhat.com/errata/RHSA-2026:51146
- access.redhat.com/errata/RHSA-2026:75652
- access.redhat.com/errata/RHSA-2026:68696
- access.redhat.com/errata/RHSA-2026:68709
- access.redhat.com/errata/RHSA-2026:68699
- access.redhat.com/errata/RHSA-2026:75659
- access.redhat.com/errata/RHSA-2026:69933
- access.redhat.com/errata/RHSA-2026:68708
- access.redhat.com/errata/RHSA-2026:69932
- access.redhat.com/errata/RHSA-2026:51100
- access.redhat.com/errata/RHSA-2026:42875
- access.redhat.com/errata/RHSA-2026:71392
- access.redhat.com/errata/RHSA-2026:71396
- aomedia.googlesource.com/aom/+/a93ba0ffaa
- access.redhat.com/errata/RHSA-2026:69935
- access.redhat.com/errata/RHSA-2026:76043
- access.redhat.com/errata/RHSA-2026:75657
- access.redhat.com/errata/RHSA-2026:71394
- access.redhat.com/errata/RHSA-2026:75654
- access.redhat.com/errata/RHSA-2026:68698
- access.redhat.com/errata/RHSA-2026:76041
- access.redhat.com/errata/RHSA-2026:71398
- access.redhat.com/errata/RHSA-2026:71397
- access.redhat.com/errata/RHSA-2026:30814
- access.redhat.com/errata/RHSA-2026:68639
- access.redhat.com/errata/RHSA-2026:61628
- access.redhat.com/errata/RHSA-2026:69931
- access.redhat.com/errata/RHSA-2026:60520
- access.redhat.com/errata/RHSA-2026:71399
- access.redhat.com/errata/RHSA-2026:75658
- access.redhat.com/errata/RHSA-2026:75660
- access.redhat.com/errata/RHSA-2026:71393
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-56211.json
- access.redhat.com/errata/RHSA-2026:68638
- access.redhat.com/errata/RHSA-2026:69927
- access.redhat.com/errata/RHSA-2026:69929
- access.redhat.com/errata/RHSA-2026:69930
- access.redhat.com/errata/RHSA-2026:68640
- issues.chromium.org/issues/503993985
- access.redhat.com/errata/RHSA-2026:61627
- access.redhat.com/errata/RHSA-2026:61629
- access.redhat.com/security/cve/CVE-2026-56211
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-108334 Github.com/kuadrant/kuadrant-operator/internal/wasm: github.com/rh-api-management/rhcl-operator-product-build/kuadrant-operator: kuadrant-operator: crafted httproute match values can bypass gateway policy overrides 1h
- Medium CVE-2026-110927 Openssh: openssh: a compressed payload can expand past the maximum packet size 6h
- Medium CVE-2026-110924 Openssh: openssh: gssapi delegated credentials can be stored after a failed authentication 6h
- Medium CVE-2026-110923 Openssh: openssh: sftp can write outside the destination directory from a server-supplied path 14h
- Medium CVE-2026-110925 Openssh: openssh: '$' and '\' in a command-line username expand through %u 14h
- Medium CVE-2026-110926 Openssh: openssh: shared lz77 compression dictionary leaks plaintext across channels 14h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-56211 is "Libaom: libaom: remote code execution via svc layer context handling with attacker-controlled frames", rated High. It affects Ai Inference Server (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.88% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.