<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>FFmpeg Versions 3.4 Through 8.1.2 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/ffmpeg-versions-3.4-through-8.1.2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 23 Jul 2026 20:21:39 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/ffmpeg-versions-3.4-through-8.1.2/feed.xml" rel="self" type="application/rss+xml"/><item><title>Out-of-Bounds Write Vulnerability in FFmpeg vf_floodfill Filter (CVE-2026-65705)</title><link>https://feed.craftedsignal.io/briefs/2026-07-ffmpeg-floodfill-oob-write/</link><pubDate>Thu, 23 Jul 2026 20:21:39 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-ffmpeg-floodfill-oob-write/</guid><description>A critical out-of-bounds write vulnerability exists in FFmpeg versions 3.4 through 8.1.2 within the vf_floodfill video filter, which attackers can exploit by providing a specially crafted, dynamically sized video stream with filtergraph reinitialization disabled via -reinit_filter 0, leading to heap corruption, a process crash, and potentially remote code execution.</description><content:encoded><![CDATA[<p>FFmpeg versions 3.4 through 8.1.2 are susceptible to a high-severity out-of-bounds write vulnerability, identified as CVE-2026-65705. This flaw resides within the <code>vf_floodfill</code> video filter component. Attackers can leverage this by crafting a malicious video stream that features dynamically sized frames. When such a stream is processed by <code>ffmpeg</code> with filtergraph reinitialization explicitly disabled (using the <code>-reinit_filter 0</code> command-line argument), the <code>filter_frame()</code> function attempts to push flood-fill neighbor data beyond the initially allocated memory boundaries. This heap corruption ultimately leads to a process crash, but depending on the heap layout and system hardening measures, it presents a significant risk for remote code execution. This vulnerability affects a wide range of FFmpeg installations, necessitating immediate patching.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts a malicious video file specifically designed with dynamically sized frames.</li>
<li>The attacker prepares the execution environment, ensuring that the <code>ffmpeg</code> command will process the malicious video with the <code>-reinit_filter 0</code> argument, which disables filtergraph reinitialization.</li>
<li>The victim executes the <code>ffmpeg</code> command with the attacker-provided video file and arguments.</li>
<li>FFmpeg begins processing the video, and the <code>vf_floodfill</code> filter allocates a traversal stack based on the dimensions of the initial frames.</li>
<li>A subsequent frame, intentionally larger than the initial frames, is processed by the <code>vf_floodfill</code> filter.</li>
<li>The <code>filter_frame()</code> function attempts to write data for flood-fill neighbors beyond the bounds of the original, smaller memory allocation.</li>
<li>This out-of-bounds write corrupts the heap memory of the <code>ffmpeg</code> process.</li>
<li>The heap corruption causes the <code>ffmpeg</code> process to crash, potentially allowing for arbitrary code execution depending on the specific memory layout and system mitigations.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-65705 leads to heap memory corruption within the FFmpeg process, causing it to crash. This results in denial of service for any service or application relying on the vulnerable FFmpeg instance for video processing. Crucially, depending on the specifics of the heap layout and the system's process hardening mechanisms, this vulnerability can be escalated to remote code execution. If exploited, an attacker could gain control over the affected system, leading to data compromise, further network intrusion, or the deployment of additional malware. The broad use of FFmpeg across various applications means the potential impact could span numerous sectors and critical systems.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2026-65705 immediately by updating all FFmpeg installations to a version beyond 8.1.2.</li>
<li>Implement host-based intrusion detection systems to monitor for unusual <code>ffmpeg</code> process crashes or unexpected terminations.</li>
<li>Configure application whitelisting to prevent the execution of <code>ffmpeg</code> with suspicious command-line arguments like <code>-reinit_filter 0</code> from untrusted sources.</li>
<li>Review and update system hardening configurations to include exploit mitigation techniques such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP), which can reduce the likelihood of successful code execution.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve</category><category>vulnerability</category><category>out-of-bounds-write</category><category>ffmpeg</category><category>video-processing</category></item></channel></rss>