CVE-2026-56208
What it is
A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when g_lag_in_frames is set to 1 or higher. This results in a 232-byte out-of-bounds write on every encoded frame after the second, corrupting adjacent heap objects. An attacker who can influence encoder configuration in a transcoding service or WebRTC session could exploit this to cause a denial of service (process crash) or potentially achieve 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.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- 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.5% in the next 30 days (EPSS).
- Severity: 7.6 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-122
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 7.6
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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-56208.md and follow it. Check whether this project is affected by CVE-2026-56208. 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:47104
- https://access.redhat.com/errata/RHSA-2026:47105
- https://access.redhat.com/errata/RHSA-2026:51100
- https://access.redhat.com/errata/RHSA-2026:51146
- https://access.redhat.com/errata/RHSA-2026:54180
- https://access.redhat.com/errata/RHSA-2026:54181
- https://access.redhat.com/errata/RHSA-2026:54182
- https://access.redhat.com/errata/RHSA-2026:54185
- https://access.redhat.com/errata/RHSA-2026:54248
- https://access.redhat.com/errata/RHSA-2026:54249
- https://access.redhat.com/errata/RHSA-2026:54259
- https://access.redhat.com/errata/RHSA-2026:54339
- 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