CVE-2026-75141

Description

A flaw was found in FFmpeg. A heap buffer overflow vulnerability exists in the hvcC box writer. A remote attacker could exploit this by providing a specially crafted HEVC (High Efficiency Video Coding) input file. This could lead to memory corruption, potentially resulting in arbitrary code execution or a denial of service.

Statement

This vulnerability is rated as Important severity because an attacker providing a malformed HEVC input stream could trigger a heap-based buffer overflow, leading to memory corruption and potential arbitrary code execution within the context of the application. Although exploitation requires the victim or an automated processing pipeline to mux an untrusted video file, the potential impact on confidentiality, integrity, and availability is substantial. In Red Hat environments, FFmpeg is not part of default base operating system installations and is predominantly distributed within specialized container images and AI workloads, limiting exposure to systems configured to ingest external multimedia.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.8N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.