CVE-2026-56210

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. The CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
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.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A heap-buffer-overflow read 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 setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory).

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 19, 2026

Last Modified

October 2, 2026

Advisory Details (4)

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

2490801 – (CVE-2026-56210) CVE-2026-56210 libaom: libaom: heap-buffer-overflow read via missing bounds check in ctrl_set_layer_id

https://bugzilla.redhat.com/show_bug.cgi?id=2490801
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-56210

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-cuda-13.0-rhel9:17881979752026-09-24redhat
redhatrhai/base-image-spyre-rhel9:17881976882026-09-24redhat
redhatrhai/base-image-tpu-rhel9:17881974922026-09-24redhat
redhatrhai/base-image-rocm-7.14-rhel9:17881980162026-09-24redhat
redhatrhai/base-image-rubin-rhel9:17881975122026-09-24redhat
redhatrhai/base-image-cuda-12.9-rhel9:17881973852026-09-24redhat
redhatrhai/base-image-cpu-rhel9:17881984072026-09-24redhat
redhatrhai/base-image-neuron-rhel9:17881984042026-09-24redhat
redhatrhai/base-image-gaudi-rhel9:17881975422026-09-24redhat
redhatrhai/base-image-rocm-7.1-rhel9:17881975492026-09-22redhat
redhatrhai/base-image-cuda-13.0-rhel9:17881977442026-09-22redhat
redhatrhai/base-image-gaudi-rhel9:17881976322026-09-22redhat
redhatrhai/base-image-rocm-6.4-rhel9:17881976772026-09-22redhat
redhatrhai/base-image-cuda-12.9-rhel9:17881996222026-09-22redhat
redhatrhai/base-image-cpu-rhel9:17881975302026-09-22redhat
redhatrhai/base-image-spyre-rhel9:17881977472026-09-22redhat
redhatrhai/base-image-tpu-rhel9:17881976802026-09-22redhat
redhatrhai/base-image-spyre-rhel9:17891376072026-09-17redhat
redhatrhaiis/vllm-cuda-rhel9:17895827762026-09-17redhat
redhatrhai/base-image-cuda-12.9-rhel9:17891376362026-09-17redhat
redhatrhaiis/model-opt-cuda-rhel9:17895082872026-09-17redhat
redhatrhaiis/vllm-spyre-rhel9:17895024932026-09-17redhat
redhatrhai/base-image-neuron-rhel9:17891375522026-09-17redhat
redhatrhai/base-image-tpu-rhel9:17891375482026-09-17redhat
redhatrhaiis/vllm-rocm-rhel9:17895043712026-09-17redhat
redhatrhai/base-image-rocm-7.0-rhel9:17891375482026-09-17redhat
redhatrhai/base-image-cuda-13.0-rhel9:17891376362026-09-17redhat
redhatrhai/base-image-rocm-6.4-rhel9:17891375482026-09-17redhat
redhatrhai/base-image-cpu-rhel9:17891376412026-09-17redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat

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.

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 10× in last 7d / 50× 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 408 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56210?
CVE-2026-56210 is a high vulnerability published on June 19, 2026. A heap-buffer-overflow read 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 setting a spatiallayerid exceeding the configured number of layers. This causes an out-of-bounds heap…
When was CVE-2026-56210 disclosed?
CVE-2026-56210 was first published on June 19, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56210 actively exploited?
CVE-2026-56210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56210?
CVE-2026-56210 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-56210?
A fix for CVE-2026-56210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56210 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-56210

Explore →

Is Your Infrastructure Affected by CVE-2026-56210?

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