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 — 4 sources updated 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
28%
KEV
Not listed

Published

June 19, 2026

Last Modified

August 18, 2026

Advisory Details (4)

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

Chromium

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

Vendor Advisories for CVE-2026-56208(15)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatfirefox-0:140.13.0-1.el9_62026-08-12redhat
redhatfirefox-0:140.13.0-1.el8_42026-08-12redhat
redhatfirefox-0:140.13.0-1.el9_42026-08-12redhat
redhatfirefox-0:140.13.0-1.el9_22026-08-12redhat
redhatfirefox-0:140.13.0-1.el10_02026-08-12redhat
redhatfirefox-0:140.13.0-1.el7_92026-08-12redhat
redhatfirefox-0:140.13.0-1.el8_62026-08-12redhat
redhatfirefox-0:140.13.0-1.el8_82026-08-12redhat
redhataom-0:3.14.0-1.el9ai2026-08-06redhat
redhatfirefox-0:140.13.0-1.el9_82026-08-03redhat
redhatfirefox-0:140.13.0-1.el8_102026-07-28redhat
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 48× in last 7d / 212× 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 343 total refreshes for this CVE.

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

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 August 18, 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 72.2% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs