CVE-2026-65705: FFmpeg 3.4 - 8.1.2 vf_floodfill Out-of-Bounds Write via filter_frame()
FFmpeg versions 3.4 through 8.1.2 contain an out-of-bounds write vulnerability in the vf_floodfill video filter that allows attackers to corrupt heap memory by supplying a dynamically sized video stream with filtergraph reinitialization disabled via -reinit_filter 0. When config_input() allocates the points traversal stack based on initial frame dimensions and a subsequent larger frame is processed, filter_frame() performs flood-fill neighbor pushes beyond the original allocation boundary, resulting in heap corruption and process crash with potential for code execution depending on heap layout and process hardening.
Security readout for executives and security teams
Plain-English summary
A specially crafted, dynamically resizing video can make FFmpeg write outside allocated memory when the floodfill filter runs with filter reinitialization disabled. This can crash media-processing services and may permit code execution, although that outcome depends on memory layout and process protections.
Executive priority
Treat as a high-priority media-processing vulnerability where untrusted uploads or feeds reach the affected configuration. Patch or remove the risky configuration promptly on exposed systems. Lower priority may be reasonable only after confirming the floodfill path is unreachable and documenting that evidence.
Technical view
In FFmpeg 3.4 through 8.1.2, vf_floodfill allocates its traversal stack from initial frame dimensions. With -reinit_filter 0, a later larger frame can cause filter_frame() to push neighboring points beyond that allocation, producing heap corruption. The issue is classified as CWE-131 and CWE-787 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is most likely in applications, pipelines, or services that process untrusted video using the floodfill filter, permit frame-size changes, and disable filtergraph reinitialization. Deployments not invoking this filter configuration may not reach the vulnerable path. Confirm bundled FFmpeg versions because applications may embed it indirectly.
Exploitation context
The supplied CVSS vector describes local attack reachability with required user interaction, no privileges, and potentially high confidentiality, integrity, and availability impact. The source bundle does not establish active exploitation, and the CVE is not listed as KEV. Potential code execution is conditional, while process crashes and heap corruption are directly supported.
Researcher notes
The vulnerable allocation-to-use relationship spans config_input() and filter_frame(): initial dimensions size the traversal stack, but later dimensions govern neighbor insertion. Source reporting names versions 3.4 through 8.1.2 and provides a patch commit, but does not identify a clearly fixed release. Validate downstream backports and vendor packaging independently.
Mitigation direction
Identify FFmpeg installations and embedded copies within media-processing products.
Prioritize systems processing untrusted media with vf_floodfill and filter reinitialization disabled.
Avoid the vulnerable filter configuration until remediation is confirmed operationally safe.
Apply an FFmpeg release containing commit f186c50cf53aec20e9a29059cb22ca3f2d59201c after vendor confirmation.
Use process isolation and least privilege to reduce consequences from malformed media.
Validation and detection
Record each FFmpeg version, build provenance, and embedded library copy.
Search application configurations for vf_floodfill and disabled filter reinitialization.
Confirm whether workflows accept untrusted videos with changing frame dimensions.
Verify the deployed build contains the cited patch commit or an equivalent vendor backport.
Run defensive regression tests using controlled media in an isolated environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-131: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-131 · source CWE mapping
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.