Arbitrary memory write via unchecked SVC layer IDs
Published Jun 19, 2026 · Updated Jun 19, 2026
Out-of-bounds write in libaom before 3.14.0 allows remote attackers to corrupt encoder memory via crafted SVC frame input. ctrl_set_layer_id accepts layer IDs outside the configured arrays, letting pixel data become the cyclic-refresh map pointer before an update writes about 1,200 bytes through it. Exploitation requires SVC to be enabled and attacker-influenced frames to reach the encoder; the write can crash the process or hijack control flow.
Summary
What happened
Out-of-bounds write in libaom before 3.14.0 allows remote attackers to corrupt encoder memory via crafted SVC frame input. ctrl_set_layer_id accepts layer IDs outside the configured arrays, letting pixel data become the cyclic-refresh map pointer before an update writes about 1,200 bytes through it. Exploitation requires SVC to be enabled and attacker-influenced frames to reach the encoder; the write can crash the process or hijack control flow.
The record
- CVE
- CVE-2026-56209
- Published
- Jun 19, 2026
- Updated
- Jun 19, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux AI
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2026CVE publishedPublication date reported by the CVE source.
- Jun 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo