Heap-based Buffer Overflow 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 applicationsSnyk Learn
Learn about Heap-based Buffer Overflow vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-LIBAOM-17660762
- published28 Jun 2026
- disclosed19 Jun 2026
- creditUnknown
Introduced: 19 Jun 2026
CVE-2026-56208 (opens in a new tab)How to fix?
There is no fixed version for libaom.
Overview
Affected versions of this package are vulnerable to Heap-based Buffer Overflow in the AV1 encoder process when the encoder is configured with g_lag_in_frames set to 1 or higher, which enables Look-Ahead Processing mode. An attacker can corrupt adjacent heap objects and potentially execute arbitrary code or cause a denial of service by providing specially crafted input that influences encoder configuration parameters. This is only exploitable if the encoder API is used with LAP mode enabled and untrusted configuration input is accepted.
Workaround
This vulnerability can be mitigated by avoiding the use of g_lag_in_frames values greater than or equal to 1 when processing untrusted input, validating all encoder configuration parameters before passing them to the API, restricting access to encoding services to trusted clients, and applying network-level access controls to limit who can submit video for encoding.