Heap corruption via stale TDSC frame buffer
Published Jul 23, 2026 · Updated Jul 23, 2026
Out-of-bounds write in FFmpeg's TDSC decoder in versions 2.7 through 8.1.2 allows remote attackers to corrupt heap memory via crafted AVI files. In tdsc_parse_tdsf(), a dimension change reuses the existing reference frame without unreferencing it before av_frame_get_buffer(), leaving tdsc_blit() and tdsc_yuv2rgb() to write pixels beyond the undersized allocation. The target must process the malicious file; successful corruption crashes the process and can execute attacker-controlled code.
Summary
What happened
Out-of-bounds write in FFmpeg's TDSC decoder in versions 2.7 through 8.1.2 allows remote attackers to corrupt heap memory via crafted AVI files. In tdsc_parse_tdsf(), a dimension change reuses the existing reference frame without unreferencing it before av_frame_get_buffer(), leaving tdsc_blit() and tdsc_yuv2rgb() to write pixels beyond the undersized allocation. The target must process the malicious file; successful corruption crashes the process and can execute attacker-controlled code.
The record
- CVE
- CVE-2026-65703
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 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=2.7 <=8.1.2
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
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