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.
CVE-2026-56209
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
July 22, 2026
Advisory Details (4)
Auto-updated Jun 22, 20262490800 – (CVE-2026-56209) CVE-2026-56209 libaom: libaom: arbitrary address write via SVC layer context OOB and cyclic refresh map pointer hijack
https://bugzilla.redhat.com/show_bug.cgi?id=2490800Vendor Advisories for CVE-2026-56209(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:42875Red Hat Product SecurityHigh
Red Hat Security Advisory: RHEL AI 3.5 RPM runtime CVE fix - aom
- RHSA-2026:30814Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- GHSA-8vmr-q5h8-3vc5GitHub Security AdvisoriesHigh
An arbitrary address write vulnerability was found in libaom, the reference AV1 codec...
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | aom-0:3.14.0-1.el9ai | 2026-07-21 | redhat |
| redhat | aom-main-3.14.0-0.1.hum1 | 2026-06-28 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 119× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 140 total refreshes for this CVE.
- 2026-07-27 06:48 UTCVendor advisory
- 2026-07-27 06:47 UTCGHSA enrichment
- 2026-07-26 16:52 UTCEG score recompute
- 2026-07-26 16:52 UTCVendor advisory
- 2026-07-26 16:52 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 20:40 UTCVendor advisory
- 2026-07-16 20:40 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 07:35 UTCVendor advisory
- 2026-07-16 07:35 UTCGHSA enrichment
- 2026-07-15 19:00 UTCVendor advisory
- 2026-07-15 19:00 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 06:25 UTCVendor advisory
- 2026-07-15 06:25 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 15:46 UTCVendor advisory
- 2026-07-14 15:46 UTCGHSA enrichment
- 2026-07-14 03:10 UTCVendor advisory
- 2026-07-14 03:10 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 14:35 UTCVendor advisory
- 2026-07-13 14:35 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 02:00 UTCVendor advisory
- 2026-07-13 02:00 UTCGHSA enrichment
- 2026-07-12 13:26 UTCVendor advisory
- 2026-07-12 13:25 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 00:49 UTCVendor advisory
- 2026-07-12 00:49 UTCGHSA enrichment
- 2026-07-11 12:15 UTCVendor advisory
- 2026-07-11 12:14 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 23:39 UTCVendor advisory
- 2026-07-10 23:39 UTCGHSA enrichment
- 2026-07-10 11:04 UTCVendor advisory
- 2026-07-10 11:04 UTCGHSA enrichment
- 2026-07-09 22:00 UTCVendor advisory
- 2026-07-09 22:00 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 09:25 UTCVendor advisory
- 2026-07-09 09:24 UTCGHSA enrichment
- 2026-07-08 20:49 UTCVendor advisory
- 2026-07-08 20:49 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 08:15 UTCVendor advisory
- 2026-07-08 08:15 UTCGHSA enrichment
- 2026-07-07 19:41 UTCVendor advisory
- 2026-07-07 19:41 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 03:00 UTCVendor advisory
- 2026-07-07 03:00 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 14:25 UTCVendor advisory
- 2026-07-06 14:24 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 01:49 UTCVendor advisory
- 2026-07-06 01:49 UTCGHSA enrichment
- 2026-07-05 13:14 UTCVendor advisory
- 2026-07-05 13:14 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:38 UTCVendor advisory
- 2026-07-05 00:38 UTCGHSA enrichment
- 2026-07-04 12:03 UTCVendor advisory
- 2026-07-04 12:03 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 23:27 UTCVendor advisory
- 2026-07-03 23:27 UTCGHSA enrichment
- 2026-07-03 10:53 UTCVendor advisory
- 2026-07-03 10:53 UTCGHSA enrichment
- 2026-07-02 21:57 UTCVendor advisory
- 2026-07-02 21:57 UTCGHSA enrichment
- 2026-07-02 09:23 UTCVendor advisory
- 2026-07-02 09:23 UTCGHSA enrichment
- 2026-07-01 20:48 UTCVendor advisory
- 2026-07-01 20:48 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-56209?
When was CVE-2026-56209 disclosed?
Is CVE-2026-56209 actively exploited?
What is the CVSS score of CVE-2026-56209?
How do I remediate CVE-2026-56209?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56209
Is Your Infrastructure Affected by CVE-2026-56209?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.