CVE-2026-56209

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

October 9, 2026

Advisory Details (4)

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

Chromium

https://issues.chromium.org/issues/503993984
Red Hat

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
Web page

a93ba0ffaa - aom - Git at Google

https://aomedia.googlesource.com/aom/+/a93ba0ffaa
Red HatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-56209(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-cpu-rhel9:17907036562026-10-05redhat
redhatrhai/base-image-spyre-rhel9:17907036302026-10-05redhat
redhatrhai/base-image-neuron-rhel9:17907035572026-10-05redhat
redhatrhai/base-image-tpu-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-rocm-7.14-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907037062026-10-05redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036452026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909541792026-10-05redhat
redhatrhelai3/bootc-rocm-rhel9:17907918932026-10-05redhat
redhatrhai/base-image-gaudi-rhel9:17907035522026-10-01redhat
redhatrhai/base-image-cuda-12.9-rhel9:17881973852026-09-24redhat
redhatrhai/base-image-cpu-rhel9:17881984072026-09-24redhat
redhatrhai/base-image-cuda-13.0-rhel9:17881979752026-09-24redhat
redhatrhai/base-image-rubin-rhel9:17881975122026-09-24redhat
redhatrhai/base-image-spyre-rhel9:17881976882026-09-24redhat
redhatrhai/base-image-neuron-rhel9:17881984042026-09-24redhat
redhatrhai/base-image-tpu-rhel9:17881974922026-09-24redhat
redhatrhai/base-image-gaudi-rhel9:17881975422026-09-24redhat
redhatrhai/base-image-rocm-7.14-rhel9:17881980162026-09-24redhat
redhatrhai/base-image-cpu-rhel9:17881975302026-09-22redhat
redhatrhai/base-image-rocm-6.4-rhel9:17881976772026-09-22redhat
redhatrhai/base-image-spyre-rhel9:17881977472026-09-22redhat
redhatrhai/base-image-cuda-13.0-rhel9:17881977442026-09-22redhat
redhatrhai/base-image-cuda-12.9-rhel9:17881996222026-09-22redhat
redhatrhai/base-image-gaudi-rhel9:17881976322026-09-22redhat
redhatrhai/base-image-tpu-rhel9:17881976802026-09-22redhat
redhatrhai/base-image-rocm-7.1-rhel9:17881975492026-09-22redhat
redhatrhaiis/vllm-cuda-rhel9:17895827762026-09-17redhat
redhatrhai/base-image-spyre-rhel9:17891376072026-09-17redhat
redhatrhai/base-image-neuron-rhel9:17891375522026-09-17redhat

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 rangeFix by version rangeDependents
aom3.6.0-1, 3.6.0-1+deb12u1, 3.6.0-1+deb12u2
  • every version up to 3.6.0-1+deb12u3: fixed in 3.6.0-1+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
aom3.12.1-1
  • every version up to 3.12.1-1+deb13u1: fixed in 3.12.1-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
aom3.12.1-1, 3.13.1-1, 3.13.1-1~exp1, 3.13.1-2
  • every version up to 3.14.1-1: fixed in 3.14.1-1
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 31× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 439 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 344 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:38 UTCEG score recompute
  2. 2026-10-11 16:53 UTCEG score recompute
  3. 2026-10-11 14:16 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-09 18:35 UTCEG score recompute
  8. 2026-10-09 18:35 UTCVendor advisory
  9. 2026-10-09 18:35 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  10. 2026-10-09 17:19 UTCEG score recompute
  11. 2026-10-09 17:19 UTCVendor advisory
  12. 2026-10-09 17:19 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-06 03:19 UTCVendor advisory
  17. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  18. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  19. 2026-10-06 03:19 UTCEG score recompute
  20. 2026-10-06 03:19 UTCVendor advisory
  21. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  22. 2026-10-06 02:35 UTCEG score recompute
  23. 2026-10-06 02:35 UTCVendor advisory
  24. 2026-10-06 02:35 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 49th percentile
Show 70 more
  1. 2026-10-05 11:31 UTCEG score recompute
  2. 2026-10-05 11:31 UTCVendor advisory
  3. 2026-10-05 11:31 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  4. 2026-10-05 10:38 UTCEG score recompute
  5. 2026-10-05 10:38 UTCVendor advisory
  6. 2026-10-05 10:38 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-02 02:19 UTCEG score recompute
  11. 2026-10-02 02:19 UTCVendor advisory
  12. 2026-10-02 02:18 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-24 09:17 UTCEG score recompute
  21. 2026-09-24 09:17 UTCVendor advisory
  22. 2026-09-24 09:17 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  23. 2026-09-24 08:29 UTCEG score recompute
  24. 2026-09-24 08:29 UTCVendor advisory
  25. 2026-09-24 08:29 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  26. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  27. 2026-09-22 13:19 UTCEG score recompute
  28. 2026-09-22 13:19 UTCVendor advisory
  29. 2026-09-22 13:18 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  30. 2026-09-22 12:22 UTCEG score recompute
  31. 2026-09-22 12:22 UTCVendor advisory
  32. 2026-09-22 12:22 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  33. 2026-09-21 11:29 UTCEG score recompute
  34. 2026-09-21 11:29 UTCVendor advisory
  35. 2026-09-21 11:29 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  36. 2026-09-21 10:45 UTCEG score recompute
  37. 2026-09-21 10:45 UTCVendor advisory
  38. 2026-09-21 10:45 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  39. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  40. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  41. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  42. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  43. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  44. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-09-14 02:14 UTCEG score recompute
  46. 2026-09-14 02:14 UTCVendor advisory
  47. 2026-09-14 02:14 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  48. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  49. 2026-09-13 13:09 UTCEG score recompute
  50. 2026-09-13 13:09 UTCVendor advisory
  51. 2026-09-13 13:09 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  52. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  54. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  55. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  56. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  57. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  58. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  59. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  60. 2026-09-01 13:44 UTCEG score recompute
  61. 2026-09-01 13:44 UTCVendor advisory
  62. 2026-09-01 13:43 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  63. 2026-09-01 12:19 UTCEG score recompute
  64. 2026-09-01 12:19 UTCVendor advisory
  65. 2026-09-01 12:19 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  66. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  67. 2026-08-31 16:23 UTCVendor advisory
  68. 2026-08-31 16:22 UTCGHSA enrichmentGHSA-8vmr-q5h8-3vc5 · GitHub severity HIGH · GitHub CVSS 7.1
  69. 2026-08-31 14:31 UTCEG score recompute
  70. 2026-08-31 14:31 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56209?
CVE-2026-56209 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-56209 was made public on June 19, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on June 19, 2026. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-56209 actively exploited?
CVE-2026-56209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56209?
CVE-2026-56209 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56209?
A fix for CVE-2026-56209 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56209 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs