Heap corruption via stale flood-fill stack allocation
Published Jul 23, 2026 · Updated Jul 23, 2026
Out-of-bounds writes in FFmpeg 3.4 through 8.1.2 allow attackers to corrupt heap memory through the vf_floodfill filter. config_input() sizes the traversal stack from the initial frame, but filter_frame() pushes neighbors from a later, larger frame past that allocation. The nondefault -reinit_filter 0 setting is required; successful triggering crashes the process, while code execution depends on heap layout and hardening.
Summary
What happened
Out-of-bounds writes in FFmpeg 3.4 through 8.1.2 allow attackers to corrupt heap memory through the vf_floodfill filter. config_input() sizes the traversal stack from the initial frame, but filter_frame() pushes neighbors from a later, larger frame past that allocation. The nondefault -reinit_filter 0 setting is required; successful triggering crashes the process, while code execution depends on heap layout and hardening.
The record
- CVE
- CVE-2026-65705
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-131, CWE-787, T1203
- 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=3.4 <=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.
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