Cyber Resilience

CVE-2026-40962

Memory Safety in Ffmpeg ≤ 8.1

Published
16 April 2026
Modified
20 April 2026
Patch / advisory
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0013 3th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2026-40962 is a medium-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Ffmpeg Ffmpeg. Its CVSS base score is 4.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-40962 is an integer overflow vulnerability in FFmpeg versions prior to 8.1, leading to an out-of-bounds write. The issue arises when processing CENC (Common Encryption) subsample data in the libavformat/mov.c component, classified under CWE-190 (Integer Overflow or Wraparound). Published on 2026-04-16, it carries a CVSS v3.1 base score of 4.9 (AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L), indicating moderate severity with low impacts across confidentiality, integrity, and availability.

Exploitation requires local access (AV:L) with no privileges (PR:N) and high attack complexity (AC:H), but no user interaction (UI:N). A successful attack could allow an unprivileged local attacker to trigger the overflow during media file parsing, potentially resulting in limited data corruption, minor information disclosure, or partial denial of service within the affected FFmpeg process.

The FFmpeg project addresses this in pull request 22348 at https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22348, with mitigation achieved by upgrading to FFmpeg 8.1 or later, which includes the necessary fixes to prevent the integer overflow and out-of-bounds write in mov.c.

EU & UK References

Vulnerability Data

FFmpeg before 8.1 has an integer overflow and resultant out-of-bounds write via CENC (Common Encryption) subsample data to libavformat/mov.c.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-36616Same product: Ffmpeg Ffmpeg
CVE-2024-35366Same product: Ffmpeg Ffmpeg
CVE-2024-22860Same product: Ffmpeg Ffmpeg
CVE-2024-36618Same product: Ffmpeg Ffmpeg
CVE-2024-36617Same product: Ffmpeg Ffmpeg
CVE-2025-63757Same product: Ffmpeg Ffmpeg
CVE-2024-36619Same product: Ffmpeg Ffmpeg
CVE-2024-22862Same product: Ffmpeg Ffmpeg
CVE-2024-22861Same product: Ffmpeg Ffmpeg
CVE-2024-35369Same product: Ffmpeg Ffmpeg

Affected Assets

ffmpeg
ffmpeg
≤ 8.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.

Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.

Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect integer overflows before release.

prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References