CVE-2026-125187
FFmpeg through 9.0.2 TTA Encoder Reachable Assertion via tta_encode_frame()
FFmpeg through 9.0.2 contains a reachable assertion vulnerability in the TTA encoder's tta_encode_frame() in libavcodec/ttaenc.c, which never reserves output packet space for the 4-byte CRC. Attackers can supply audio whose sample values and length produce a small, poorly compressible final frame, triggering the av_assert0() in flush_put_bits() and aborting applications transcoding to TTA.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: VulnCheckAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| FFmpeg FFmpeg ffmpeg/ffmpeg
github |
≥ 0; ≤ 9.0.2 (affected, semver)
Other versions: unaffected |
CNA: VulnCheck |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 6.8 medium |
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA: VulnCheck |
| 3.1 / 5.5 medium |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | CNA: VulnCheck |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/25694CNA: VulnCheck · issue-tracking
- https://github.com/FFmpeg/FFmpeg/commit/29a629e788c4343ff2e923095b8f38769fe2e470CNA: VulnCheck · patch
- https://github.com/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/ttaenc.c#L93CNA: VulnCheck · technical-description
- https://github.com/FFmpeg/FFmpegCNA: VulnCheck · product
- https://www.vulncheck.com/advisories/ffmpeg-through-9.0.2-tta-encoder-reachable-assertion-via-tta-encode-frameCNA: VulnCheck · third-party-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.