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-17660763
- published28 Jun 2026
- disclosed19 Jun 2026
- creditUnknown
Introduced: 19 Jun 2026
CVE-2026-56211 (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 layer context handling process. An attacker can achieve arbitrary command execution by supplying crafted video frames with attacker-controlled pixel values that overlap with internal encoder context structures, hijacking internal pointers, and leveraging a crash oracle to brute-force ASLR in fork-based video processing services. This is only exploitable if the target service uses a fork-based architecture with SVC encoding enabled and accepts attacker-supplied video frames.
Workaround
This vulnerability can be mitigated by validating all SVC layer parameters (such as spatial_layer_id and temporal_layer_id) against configured bounds before passing them to the encoder API, avoiding fork-based architectures for encoding services that accept untrusted input, restricting access to encoding services to trusted clients only, and enabling all available exploit mitigations (ASLR, PIE, stack canaries, CFI) on encoding service binaries.