CVE-2026-56208 | Libaom: libaom: heap buffer overflow in av1 encoder first-pass stats buffer via lap mode

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.

Published: 2026-06-19 Last update: 2026-06-22 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-56208 is rated Low Risk (36.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.27%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-56208

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-23 — 0.27% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-56208

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 4.7 [email protected]

Weakness enumeration for CVE-2026-56208

GitHub Security Advisory for CVE-2026-56208

GHSA-mgv2-4j37-m3x6 · Severity: high — A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation....

OS Trackers for CVE-2026-56208

vendor priority summary link
debian not yet assigned CVE-2026-56208 not yet assigned priority: Debian including 1 source packages (aom), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2026-56208
redhat high — https://access.redhat.com/security/cve/CVE-2026-56208
suse high CVE-2026-56208 severity important: SUSE including 2 source package names (libaom, libaom0), 4 product×package rows across 2 product lines (SUSE Linux Enterprise Server 15 SP2-LTSS, SUSE Linux Enterprise Server 15 SP3-LTSS): Known Not Affected 4. https://www.suse.com/security/cve/CVE-2026-56208/

Affected software / configurations for CVE-2026-56208

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-56208

cvelogic Threat Intelligence