FFmpeg up to 8.x RSCC Decoder libavcodec/rscc.c rscc_decode_frame inflated_buf uninitialized pointer

Summaryinfo

A vulnerability marked as critical has been reported in FFmpeg up to 8.x. This affects the function rscc_decode_frame of the file libavcodec/rscc.c of the component RSCC Decoder. This manipulation of the argument inflated_buf causes uninitialized pointer. This vulnerability is registered as CVE-2026-70629. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in FFmpeg up to 8.x. It has been declared as critical. Affected by this vulnerability is the function rscc_decode_frame of the file libavcodec/rscc.c of the component RSCC Decoder. The manipulation of the argument inflated_buf with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

FFmpeg versions from 3.0 up to, but not including, 9.0 contain an uninitialized heap memory read vulnerability in the native RSCC decoder (libavcodec/rscc.c) that allows attackers to disclose heap memory contents by supplying a crafted video file with a compressed tile that decompresses fewer bytes than the declared tile geometry requires. When rscc_decode_frame() calls av_image_copy_plane() without validating the decompressed byte count against the tile dimensions, the unwritten suffix of the persistent intermediate buffer ctx->inflated_buf is copied into the decoded frame, potentially exposing data from prior heap allocations or previous decoded frames in persistent decoding services.

The advisory is shared at code.ffmpeg.org. This vulnerability is known as CVE-2026-70629 since 08/04/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/07/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 8.x

License

• open-source

Website

• Product: https://ffmpeg.org/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion