Heap corruption via stale vf_quirc buffer sizing
Published Jul 24, 2026 · Updated Jul 24, 2026
Heap out-of-bounds write in FFmpeg 7.0 through 8.1.2 allows attackers to corrupt memory via a crafted PGS/SUP subtitle file. The vf_quirc filter retains the first frame's libquirc grayscale buffer and passes a larger later frame to av_image_copy_plane() without resizing that buffer. Processing a subtitle whose later presentation has larger dimensions can crash the process and permits code execution through heap corruption.
Summary
What happened
Heap out-of-bounds write in FFmpeg 7.0 through 8.1.2 allows attackers to corrupt memory via a crafted PGS/SUP subtitle file. The vf_quirc filter retains the first frame's libquirc grayscale buffer and passes a larger later frame to av_image_copy_plane() without resizing that buffer. Processing a subtitle whose later presentation has larger dimensions can crash the process and permits code execution through heap corruption.
The record
- CVE
- CVE-2026-66041
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=7.0 <=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
- FFmpeg PR 23625 out-of-array-access reproducerproof of concept · unverified
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