CVE-2026-56209
What it is
An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-56209.md and follow it. Check whether this project is affected by CVE-2026-56209. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://access.redhat.com/errata/RHSA-2026:30814
- https://access.redhat.com/errata/RHSA-2026:42875
- https://access.redhat.com/errata/RHSA-2026:51100
- https://access.redhat.com/errata/RHSA-2026:51146
- https://access.redhat.com/errata/RHSA-2026:60520
- https://access.redhat.com/errata/RHSA-2026:61627
- https://access.redhat.com/errata/RHSA-2026:61628
- https://access.redhat.com/errata/RHSA-2026:61629
- https://access.redhat.com/errata/RHSA-2026:68634
- https://access.redhat.com/errata/RHSA-2026:68637
- https://access.redhat.com/errata/RHSA-2026:68638
- https://access.redhat.com/errata/RHSA-2026:68639
- https://access.redhat.com/errata/RHSA-2026:68640
- https://access.redhat.com/errata/RHSA-2026:68696
- https://access.redhat.com/errata/RHSA-2026:68697
- https://access.redhat.com/errata/RHSA-2026:68698
- https://access.redhat.com/errata/RHSA-2026:68699
- https://access.redhat.com/errata/RHSA-2026:68708
- https://access.redhat.com/errata/RHSA-2026:68709
- https://access.redhat.com/errata/RHSA-2026:68710
- https://access.redhat.com/errata/RHSA-2026:69927
- https://access.redhat.com/errata/RHSA-2026:69929
- https://access.redhat.com/errata/RHSA-2026:69930
- https://access.redhat.com/errata/RHSA-2026:69931
- https://access.redhat.com/errata/RHSA-2026:69932