Memory corruption via unchecked RASC row-boundary access
Published Jun 28, 2026 · Updated Jun 28, 2026
Out-of-bounds write in FFmpeg's RASC decoder allows remote attackers to corrupt memory with a crafted RASC media stream. decode_dlta performs four-byte reads and writes at a PAL8 row cursor before checking whether the access crosses the row boundary. The stream must reach a build with the RASC decoder enabled; the public proof hijacks an adjacent callback only under a controlled buffer layout.
Summary
What happened
Out-of-bounds write in FFmpeg's RASC decoder allows remote attackers to corrupt memory with a crafted RASC media stream. decode_dlta performs four-byte reads and writes at a PAL8 row cursor before checking whether the access crosses the row boundary. The stream must reach a build with the RASC decoder enabled; the public proof hijacks an adjacent callback only under a controlled buffer layout.
The record
- CVE
- CVE-2026-58049
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 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 <=bcd2c69e087a09b07cf45c6bd2428ee1ccb2925c
What conditions does exploitation require?
What is affected?
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
- FFmpeg RASC DLTA Calculator PoCproof of concept · demonstrated
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