CVE-2026-56210

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH 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 — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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.1(high)
EPSS
15.8%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 22, 2026

Advisory Details (4)

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

Chromium

https://issues.chromium.org/issues/503975732
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

Vendor Advisories for CVE-2026-56210(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 123× 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 130 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database on June 19, 2026, with the most recent update on July 22, 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 15.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56210?
CVE-2026-56210 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-56210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56210, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs