Heap corruption via undersized line-history buffers
Published Jul 24, 2026 · Updated Jul 24, 2026
Heap out-of-bounds write in FFmpeg 8.1.2 and earlier allows remote attackers to corrupt heap memory via a crafted video. The vf_hqdn3d config_input path sizes per-plane line-history buffers from the initial width, while denoise_spatial writes later wider frames into them. Exploitation requires hqdn3d processing with filtergraph reinitialization disabled; the overwrite supports a process crash or arbitrary code execution.
Summary
What happened
Heap out-of-bounds write in FFmpeg 8.1.2 and earlier allows remote attackers to corrupt heap memory via a crafted video. The vf_hqdn3d config_input path sizes per-plane line-history buffers from the initial width, while denoise_spatial writes later wider frames into them. Exploitation requires hqdn3d processing with filtergraph reinitialization disabled; the overwrite supports a process crash or arbitrary code execution.
The record
- CVE
- CVE-2026-66036
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-122, 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=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
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