CVE-2026-125201: FFmpeg 7.0 before 8.1.3 and 9.x before 9.0.2 Heap Overflow via vulkan_av1.c

Q: Which deployments are exposed to this issue?

The affected ranges are FFmpeg 7.0 before 8.1.3 and FFmpeg 9.x before 9.0.2. Exposure requires AV1 content to be decoded through FFmpeg's Vulkan hardware accelerator.

Q: What must an attacker provide to trigger the vulnerability?

An attacker must cause decoding of a crafted AV1 stream containing more than 256 tiles through the Vulkan AV1 decoder path. The provided vector indicates local access, high attack complexity, no privileges required, and user interaction.

Q: What can be done if upgrading is not immediately possible?

Avoid decoding untrusted AV1 streams using the Vulkan hardware accelerator until FFmpeg can be updated. This mitigates the vulnerable vk_av1_decode_slice() path described in the advisory.

Q: How can I determine whether a system may be affected?

Check the installed FFmpeg version and whether the deployment uses Vulkan-accelerated AV1 decoding. Versions in the stated affected ranges that decode AV1 through that accelerator may be vulnerable.

Published Nov 9, 2026

Updated

FFmpeg 7.0 before 8.1.3 and 9.x before 9.0.2 contains a heap out-of-bounds write vulnerability in vkav1decodeslice() in libavcodec/vulkanav1.c because the tile-count limit is checked only on entry. Attackers can supply a crafted AV1 stream with more than 256 tiles decoded via the Vulkan hardware accelerator to overflow tilesizes and corrupt heap memory.

Affected Software

1 affected component

FFmpeg FFmpeg>=7.0<8.1.3, >=9.0<9.0.2

Event History

Nov 9, 2026

CVE Published

via MITRE·07:11 PM

Data Sourced

via MITRE·07:11 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·07:16 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are exposed to this issue?

The affected ranges are FFmpeg 7.0 before 8.1.3 and FFmpeg 9.x before 9.0.2. Exposure requires AV1 content to be decoded through FFmpeg's Vulkan hardware accelerator.

What must an attacker provide to trigger the vulnerability?

An attacker must cause decoding of a crafted AV1 stream containing more than 256 tiles through the Vulkan AV1 decoder path. The provided vector indicates local access, high attack complexity, no privileges required, and user interaction.

What can be done if upgrading is not immediately possible?

Avoid decoding untrusted AV1 streams using the Vulkan hardware accelerator until FFmpeg can be updated. This mitigates the vulnerable vk_av1_decode_slice() path described in the advisory.

How can I determine whether a system may be affected?

Check the installed FFmpeg version and whether the deployment uses Vulkan-accelerated AV1 decoding. Versions in the stated affected ranges that decode AV1 through that accelerator may be vulnerable.

CVE-2026-125201: FFmpeg 7.0 before 8.1.3 and 9.x before 9.0.2 Heap Overflow via vulkan_av1.c

Affected Software

Event History

Frequently Asked Questions

Which deployments are exposed to this issue?

What must an attacker provide to trigger the vulnerability?

What can be done if upgrading is not immediately possible?

How can I determine whether a system may be affected?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this issue?

What must an attacker provide to trigger the vulnerability?

What can be done if upgrading is not immediately possible?

How can I determine whether a system may be affected?