CVE-2026-65703: FFmpeg 2.7 - 8.1.2 Out-of-Bounds Write in TDSC Video Decoder
FFmpeg versions 2.7 through 8.1.2 contain an out-of-bounds write vulnerability in the TDSC video decoder that allows remote attackers to cause heap corruption by supplying a crafted AVI file that changes frame dimensions across TDSF frames. The tdsc_parse_tdsf() function fails to unreference the existing reference frame before calling av_frame_get_buffer(), causing tdsc_blit() and tdsc_yuv2rgb() to write attacker-controlled pixel data beyond the end of the undersized reference frame buffer, resulting in a process crash and potential code execution.
Security readout for executives and security teams
Plain-English summary
A crafted AVI file can corrupt memory when an affected FFmpeg installation decodes TDSC video. Processing the file may crash the application and could potentially allow attacker-controlled code execution. Services that automatically accept or process media from untrusted sources face the greatest business risk.
Executive priority
Prioritize internet-facing and automated media-processing systems, especially those handling customer-supplied files. Remediate promptly because exploitation could affect confidentiality, integrity, and availability. Track vendor confirmation carefully because the supplied evidence names a patch commit but no first fixed release.
Technical view
FFmpeg 2.7 through 8.1.2 fails to release an existing reference frame before reallocating after TDSF dimension changes. The resulting undersized buffer allows tdsc_blit() and tdsc_yuv2rgb() to write pixel data out of bounds, causing heap corruption. The supplied CVSS 4.0 score is 8.5.
Likely exposure
Exposure is plausible in affected FFmpeg deployments that decode untrusted AVI files, including media ingestion, transcoding, thumbnailing, analysis, and playback workflows. The bundle identifies versions 2.7 through 8.1.2 as vulnerable but does not identify a first fixed release.
Exploitation context
Exploitation requires an affected process to parse a crafted AVI containing TDSF frames with changing dimensions. The supplied vector specifies local attack delivery and passive user interaction. Successful triggering can crash the process and may permit code execution. The bundle reports no CISA KEV listing or other evidence of active exploitation.
Researcher notes
The defect is CWE-787 in the TDSC decoder’s reference-frame lifecycle. Dimension changes across TDSF frames leave an undersized allocation, followed by attacker-influenced pixel writes. Potential code execution is reported, but the bundle provides no demonstrated exploit, active-exploitation evidence, or confirmed fixed release number.
Mitigation direction
Update to a vendor-supported FFmpeg build confirmed to incorporate the referenced patch.
Backport the referenced patch when an immediate supported release upgrade is unavailable.
Temporarily restrict untrusted AVI processing until affected systems are remediated.
Isolate media-processing services and minimize their filesystem, network, and execution privileges.
Validation and detection
Inventory FFmpeg versions and embedded copies across media-processing applications and services.
Confirm whether each deployed build includes commit fd3ee52fab34d98a95b787d0b5ff45685766200c.
Identify workflows that accept or automatically decode AVI files from untrusted sources.
Review crash and memory-safety telemetry associated with AVI or TDSC decoding.
Retest normal TDSC decoding after remediation using approved, non-malicious media samples.
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-787: 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.
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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.