CVE-2026-56208

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. a secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.6EG
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.6Exploit: None knownExposed: 0

A fix is available — apply it.

A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when g_lag_in_frames is set to 1 or higher. This results in a 232-byte out-of-bounds write on every encoded frame after the second, corrupting adjacent heap objects. An attacker who can influence encoder configuration in a transcoding service or WebRTC session could exploit this to cause a denial of service (process crash) or potentially achieve code execution.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 22, 2026

Advisory Details (4)

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

2490799 – (CVE-2026-56208) CVE-2026-56208 libaom: libaom: heap buffer overflow in AV1 encoder first-pass stats buffer via LAP mode

https://bugzilla.redhat.com/show_bug.cgi?id=2490799
generic

243f8ae84b - aom - Git at Google

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

cve-details

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhataom-0:3.14.0-1.el9ai2026-07-21redhat
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 13× in last 7d / 121× 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 142 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56208?
CVE-2026-56208 is a high vulnerability published on June 19, 2026. A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when glagin_frames is set to 1 or higher. This results in a…
When was CVE-2026-56208 disclosed?
CVE-2026-56208 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-56208 actively exploited?
CVE-2026-56208 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 80.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56208?
CVE-2026-56208 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-56208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56208, 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-56208

Explore →

Is Your Infrastructure Affected by CVE-2026-56208?

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