CVE-2026-75142

FFmpeg Stack Buffer Overflow in MPEG-PS Muxer via mpegenc.c

Published Aug 19, 2026 CVSS 4.0 · 8.5 High EPSS < 1% KEV · Not listed
Description
FFmpeg before commit 9d786e4 contains a stack buffer overflow in the MPEG-PS muxer (libavformat/mpegenc.c). When muxing input with more streams than the muxer's fixed-size stack buffer accommodates, the buffer is overflowed. A crafted input with an excessive number of streams triggers the overflow during MPEG-PS muxing.

Analysis

AI-generated

Technical impact

FFmpeg versions prior to commit 9d786e4 contain a stack buffer overflow in the MPEG-PS muxer (libavformat/mpegenc.c). When an input file is parsed that contains more streams than the muxer's fixed-size stack buffer can hold, the overflow occurs during the creation of the MPEG-PS file header. This flaw can be triggered by an attacker who owns or controls the input file, allowing arbitrary code execution or denial of service if the overflow corrupts critical data structures. The weakness corresponds to an unchecked buffer write (CWE-120 and CWE-121).

Affected Systems

The vulnerability impacts the FFmpeg project, affecting all binaries built from source before the commit that introduces the fix (9d786e4b5e9b8482651928574de33772aeee7be1). Users of pre-release or older stable releases should verify the used version. The vulnerability specifically pertains to the MPEG-PS muxer component of FFmpeg.

Risk and Exploitability

The CVSS base score is 8.5, indicating a high severity. The EPSS score is less than 1%, indicating a very low likelihood of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is through a crafted media file that contains an excessive number of streams; when ffmpeg processes this file, the stack buffer overflows. The flaw affects the integrity of the program’s execution environment, and an attacker who can provide such a file to ffmpeg can gain local code execution on the host running the process.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update FFmpeg to a release that includes the commit after 9d786e4b5e9b8482651928574de33772aeee7be1.
  • Prior to launching ffmpeg, perform a sanity check on the input file to ensure the number of media streams does not exceed the tool’s documented limits, or use a wrapper script to enforce a maximum stream count.
  • If upgrading immediately is impractical, execute ffmpeg within a sandboxed or containerized environment and ensure that untrusted media files are processed in isolation from critical system resources.

Generated by OpenCVE AI on August 28, 2026 at 19:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8716-2 FFmpeg vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:ffmpeg:ffmpeg:-:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ffmpeg
Ffmpeg ffmpeg
Vendors & Products Ffmpeg
Ffmpeg ffmpeg
Type Values Removed Values Added
Description FFmpeg before commit 9d786e4 contains a stack buffer overflow in the MPEG-PS muxer (libavformat/mpegenc.c). When muxing input with more streams than the muxer's fixed-size stack buffer accommodates, the buffer is overflowed. A crafted input with an excessive number of streams triggers the overflow during MPEG-PS muxing.
Title FFmpeg Stack Buffer Overflow in MPEG-PS Muxer via mpegenc.c
Weaknesses CWE-121
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.5, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-121

    Stack-based Buffer Overflow

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 27, 2026, 10:14 AM
Reserved
Aug 17, 2026, 6:39 PM
Status
Awaiting Analysis
Published
Aug 19, 2026, 5:21 PM
Modified
Oct 26, 2026, 11:10 AM
Severity
Important
Public date
Aug 19, 2026, 4:24 PM