Quick answers
- Is CVE-2026-125257 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125257 being exploited in the wild.
- How severe is CVE-2026-125257?
- High severity, with a CVSS score of 7, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg through 9.0.2.
- Is there a fix for CVE-2026-125257?
- Yes: fixed in FFmpeg 9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125257 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125257?
- Check whether you run Ffmpeg at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: FFmpeg 9.1
Technical details
An off-by-one error in the get_exponent_dynamic() function in libavcodec/nellymoserenc.c allows the trellis index (idx) to equal OPT_SIZE instead of remaining below it, causing a write one element past the opt and path heap allocations. The vulnerability is triggered when encoding Nellymoser audio with trellis enabled and requires attacker-supplied crafted audio input. The overflow corrupts adjacent heap memory and was fixed in FFmpeg 9.1.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-09-19: patched