CVE-2026-56209

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

June 19, 2026

Last Modified

August 27, 2026

Advisory Details (4)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
generic

Chromium

https://issues.chromium.org/issues/503993984
redhat

2490800 – (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=2490800
generic

a93ba0ffaa - aom - Git at Google

https://aomedia.googlesource.com/aom/+/a93ba0ffaa
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-56209

Vendor Advisories for CVE-2026-56209(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhataom-0:3.14.0-1.el9ai2026-08-06redhat
redhataom-main-3.14.0-0.1.hum12026-06-28redhat

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
aom3.10.0-1 ... 3.9.1-1~exp1 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
aom3.12.1-13.12.1-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
aom3.12.1-1, 3.13.1-1, 3.13.1-1~exp1, 3.13.1-23.14.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 182× 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 328 total refreshes for this CVE.

  1. 2026-08-27 18:02 UTCEG score recompute
  2. 2026-08-27 18:02 UTCVendor advisory
  3. 2026-08-27 18:02 UTCGHSA enrichment
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-25 02:54 UTCEG score recompute
  8. 2026-08-25 02:54 UTCVendor advisory
  9. 2026-08-25 02:54 UTCGHSA enrichment
  10. 2026-08-24 14:18 UTCEG score recompute
  11. 2026-08-24 14:18 UTCVendor advisory
  12. 2026-08-24 14:18 UTCGHSA enrichment
  13. 2026-08-24 01:09 UTCVendor advisory
  14. 2026-08-24 01:09 UTCGHSA enrichment
  15. 2026-08-23 12:21 UTCEG score recompute
  16. 2026-08-23 12:21 UTCVendor advisory
  17. 2026-08-23 12:21 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 23:47 UTCEG score recompute
  20. 2026-08-22 23:47 UTCVendor advisory
  21. 2026-08-22 23:47 UTCGHSA enrichment
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 22:29 UTCVendor advisory
  24. 2026-08-21 22:29 UTCGHSA enrichment
  25. 2026-08-21 09:27 UTCEG score recompute
Show 75 more
  1. 2026-08-21 09:27 UTCVendor advisory
  2. 2026-08-21 09:27 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 20:41 UTCVendor advisory
  5. 2026-08-20 20:41 UTCGHSA enrichment
  6. 2026-08-20 08:04 UTCEG score recompute
  7. 2026-08-20 08:04 UTCVendor advisory
  8. 2026-08-20 08:04 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 07:07 UTCEG score recompute
  11. 2026-08-19 07:07 UTCVendor advisory
  12. 2026-08-19 07:07 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 12:15 UTCEG score recompute
  15. 2026-08-18 12:15 UTCVendor advisory
  16. 2026-08-18 12:15 UTCGHSA enrichment
  17. 2026-08-18 09:29 UTCEG score recompute
  18. 2026-08-18 09:29 UTCVendor advisory
  19. 2026-08-18 09:29 UTCGHSA enrichment
  20. 2026-08-18 08:51 UTCEG score recompute
  21. 2026-08-18 08:51 UTCVendor advisory
  22. 2026-08-18 08:51 UTCGHSA enrichment
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 06:12 UTCVendor advisory
  25. 2026-08-17 06:12 UTCGHSA enrichment
  26. 2026-08-16 17:14 UTCEG score recompute
  27. 2026-08-16 17:14 UTCVendor advisory
  28. 2026-08-16 17:14 UTCGHSA enrichment
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 04:40 UTCEG score recompute
  31. 2026-08-16 04:40 UTCVendor advisory
  32. 2026-08-16 04:40 UTCGHSA enrichment
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 16:06 UTCVendor advisory
  35. 2026-08-15 16:06 UTCGHSA enrichment
  36. 2026-08-15 03:30 UTCEG score recompute
  37. 2026-08-15 03:30 UTCVendor advisory
  38. 2026-08-15 03:30 UTCGHSA enrichment
  39. 2026-08-15 01:30 UTCEPSS rescore
  40. 2026-08-14 14:55 UTCVendor advisory
  41. 2026-08-14 14:55 UTCGHSA enrichment
  42. 2026-08-14 02:20 UTCEG score recompute
  43. 2026-08-14 02:20 UTCVendor advisory
  44. 2026-08-14 02:20 UTCGHSA enrichment
  45. 2026-08-13 22:00 UTCEPSS rescore
  46. 2026-08-13 13:46 UTCVendor advisory
  47. 2026-08-13 13:46 UTCGHSA enrichment
  48. 2026-08-13 01:10 UTCEG score recompute
  49. 2026-08-13 01:10 UTCVendor advisory
  50. 2026-08-13 01:10 UTCGHSA enrichment
  51. 2026-08-12 13:51 UTCEPSS rescore
  52. 2026-08-12 12:36 UTCEG score recompute
  53. 2026-08-12 12:36 UTCVendor advisory
  54. 2026-08-12 12:36 UTCGHSA enrichment
  55. 2026-08-12 12:11 UTCEG score recompute
  56. 2026-08-12 12:11 UTCVendor advisory
  57. 2026-08-12 12:11 UTCGHSA enrichment
  58. 2026-08-12 10:55 UTCVendor advisory
  59. 2026-08-12 10:55 UTCGHSA enrichment
  60. 2026-08-11 22:20 UTCEG score recompute
  61. 2026-08-11 22:20 UTCVendor advisory
  62. 2026-08-11 22:20 UTCGHSA enrichment
  63. 2026-08-11 22:10 UTCEG score recompute
  64. 2026-08-11 22:10 UTCVendor advisory
  65. 2026-08-11 22:10 UTCGHSA enrichment
  66. 2026-08-11 18:36 UTCEG score recompute
  67. 2026-08-11 18:36 UTCVendor advisory
  68. 2026-08-11 18:36 UTCGHSA enrichment
  69. 2026-08-11 06:01 UTCEG score recompute
  70. 2026-08-11 06:01 UTCVendor advisory
  71. 2026-08-11 06:01 UTCGHSA enrichment
  72. 2026-08-11 00:00 UTCEPSS rescore
  73. 2026-08-10 17:27 UTCVendor advisory
  74. 2026-08-10 17:27 UTCGHSA enrichment
  75. 2026-08-10 03:17 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56209?
CVE-2026-56209 is a high vulnerability published on June 19, 2026. 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…
When was CVE-2026-56209 disclosed?
CVE-2026-56209 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56209 actively exploited?
CVE-2026-56209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-56209?
CVE-2026-56209 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-56209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56209, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56209

Explore →

Is Your Infrastructure Affected by CVE-2026-56209?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs