---
title: "CVE-2026-125181: FFmpeg - Out of Bounds Write"
description: "FFmpeg <= 9.0.2 contains an out-of-bounds write caused by a non-terminating byte-swap loop in flic_decode_frame_15_16BPP() in libavcodec/flicvideo.c, letting attackers corrupt heap memory on big-endian builds, exploit requires crafted 15/16 bpp FLIC/FLX file."
url: https://panop.io/threat-heartbeat/CVE-2026-125181/
---

# CVE-2026-125181 FFmpeg - Out of Bounds Write

FFmpeg <= 9.0.2 contains an out-of-bounds write caused by a non-terminating byte-swap loop in flic\_decode\_frame\_15\_16BPP() in libavcodec/flicvideo.c, letting attackers corrupt heap memory on big-endian builds, exploit requires crafted 15/16 bpp FLIC/FLX file.

CVSS base score 7.0 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.13% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-125181)

## Details

Type

Out of Bounds Write

Impact

Denial Of Service

CVSS vector

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

Published

9 November 2026

Updated

11 November 2026

Weakness

[CWE-787](https://cwe.mitre.org/data/definitions/787.html)

## Vendor fix

Update to a version later than 9.0.2 or the latest available version.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-125181](https://nvd.nist.gov/vuln/detail/CVE-2026-125181)
- [https://www.vulncheck.com/advisories/ffmpeg-through-9.0.2-flic-decoder-out-of-bounds-write-via-fli-brun-byte-swap](https://www.vulncheck.com/advisories/ffmpeg-through-9.0.2-flic-decoder-out-of-bounds-write-via-fli-brun-byte-swap)
- [https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24901](https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24901)
- [https://github.com/FFmpeg/FFmpeg](https://github.com/FFmpeg/FFmpeg)
- [https://github.com/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/flicvideo.c#L883](https://github.com/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/flicvideo.c#L883)
- [https://github.com/FFmpeg/FFmpeg/commit/c0d308a9a616f4abcc4e0a4d86f7de92ecdef9f6](https://github.com/FFmpeg/FFmpeg/commit/c0d308a9a616f4abcc4e0a4d86f7de92ecdef9f6)
- [https://github.com/FFmpeg/FFmpeg/commit/eb47d7bb6cf13042c6ab14e22fc0c0c3a6e51e12](https://github.com/FFmpeg/FFmpeg/commit/eb47d7bb6cf13042c6ab14e22fc0c0c3a6e51e12)
- [https://github.com/FFmpeg/FFmpeg/commit/ee30fb98c0d4e97abbd5e371d2a3a926e92bec70](https://github.com/FFmpeg/FFmpeg/commit/ee30fb98c0d4e97abbd5e371d2a3a926e92bec70)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
