CVE-2026-56208
HighCVSS 7.6Exploitation Probability (EPSS)
Low risk35th percentile - higher than 35% of all known CVEs
Summary
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.
Risk Assessment
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.
Recommendation
Update libaom to a patched version immediately.
Other vulnerabilities in libaom
See all- CVE-2026-56211High
The libaom library (reference AV1 codec implementation) contains a remote code execution vulnerability. Insufficient bounds validation in the AV1 encoder's SVC layer ID control allows an attacker to supply crafted video frames that can overwrite encoder context structures.
- CVE-2026-56210High
A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers, causing an out-of-bounds heap read of approximately 40,728 bytes.
- CVE-2026-56209High
An arbitrary address write vulnerability in libaom, the reference AV1 codec implementation, allows an attacker to inject an arbitrary pointer into the cyclic refresh map field via a missing bounds check in the SVC layer ID control function. 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.
Original NVD description (English source)
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.