CVE-2026-56209 | Libaom: libaom: arbitrary address write via svc layer context oob and cyclic refresh map pointer hijack

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.

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

CVE-2026-56209 is rated Low Risk (34.6/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-56209

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-56209

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:N)
Doesn’t really leak secrets in a meaningful way.
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.2 [email protected]
7.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:N)
Doesn’t really leak secrets in a meaningful way.
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.2 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

Weakness enumeration for CVE-2026-56209

GitHub Security Advisory for CVE-2026-56209

GHSA-8vmr-q5h8-3vc5 · Severity: high — An arbitrary address write vulnerability was found in libaom, the reference AV1 codec...

OS Trackers for CVE-2026-56209

vendor priority summary link
debian unimportant CVE-2026-56209 unimportant priority: Debian including 1 source packages (aom), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 4, resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-56209
redhat high — https://access.redhat.com/security/cve/CVE-2026-56209
suse high CVE-2026-56209 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-56209/
ubuntu medium CVE-2026-56209 medium priority: Ubuntu including 1 source packages (aom), 6 status rows across 6 suites (focal, jammy, noble, questing, resolute, upstream): needs-triage 6. https://ubuntu.com/security/CVE-2026-56209

Affected software / configurations for CVE-2026-56209

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-56209

cvelogic Threat Intelligence