Out-of-bounds Write Affecting libaom package, versions [0,]
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-LIBAOM-17660764
- published28 Jun 2026
- disclosed19 Jun 2026
- creditUnknown
Introduced: 19 Jun 2026
CVE-2026-56209 (opens in a new tab)How to fix?
There is no fixed version for libaom.
Overview
Affected versions of this package are vulnerable to Out-of-bounds Write in the SVC encoder process due to a missing bounds check in the layer ID control, which allows injection of an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. An attacker can achieve arbitrary memory writes and potentially hijack control flow by supplying specially crafted frames with attacker-controlled layer configuration and pixel data to a service exposing the vulnerable encoder API. This is only exploitable if the SVC encoder feature is enabled and the attacker can control both the layer_id configuration and the image frame pixel values.
Workaround
This vulnerability can be mitigated by validating that spatial_layer_id and temporal_layer_id values are within the configured range before calling the relevant control function, and by restricting access to encoding services to trusted clients only. Deploying with ASLR, stack canaries, and other exploit mitigation technologies can also reduce risk.