Memory corruption via FAAD2 decoder bounds errors
Published Jan 27, 2026 · Updated Jan 27, 2026
Memory corruption in anyRTC anyLive before 1.0 allows local users to read or overwrite heap memory by opening crafted AAC media. The bundled FAAD2 faad_resetbits function subtracts a bitstream-derived offset from buffer_size before validating it, while excluded_channels writes past exclude_mask without enforcing MAX_CHANNELS. Exploitation requires active user interaction with attacker-controlled media; the public patch establishes out-of-bounds access but not reliable code execution.
Summary
What happened
Memory corruption in anyRTC anyLive before 1.0 allows local users to read or overwrite heap memory by opening crafted AAC media. The bundled FAAD2 faad_resetbits function subtracts a bitstream-derived offset from buffer_size before validating it, while excluded_channels writes past exclude_mask without enforcing MAX_CHANNELS. Exploitation requires active user interaction with attacker-controlled media; the public patch establishes out-of-bounds access but not reliable code execution.
The record
- CVE
- CVE-2026-1465
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- anyRTC
- Product
- anyLive
- Classifications
- CWE-119
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0
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.
Weakness, pattern, technique
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