cve.bz

CVE-2026-125073 ffmpeg ffmpeg: Infinite Loop

6.8 mediumEPSS 0.2%

Medium (6.8) in ffmpeg ffmpeg. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
FFmpeg through 9.0.2 contains an infinite loop vulnerability in bit_allocation() in libavcodec/imc.c that allows attackers to hang decoding by supplying audio blocks with a negative bit budget. Attackers can craft IMC or IAC audio files that drive freebits negative, causing the reduction loop to never terminate and consuming 100% CPU.

Severity

CVSS 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

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-125073 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125073?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125073?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125073 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125073

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125073](https://cve.bz/cve/badge/CVE-2026-125073.svg)](https://cve.bz/cve/CVE-2026-125073)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125073"><img src="https://cve.bz/cve/badge/CVE-2026-125073.svg" alt="CVE-2026-125073"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
FFmpegthrough 9.0.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreffmpegno fix listedUBUNTU-CVE-2026-125073

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

References

Check your stackJSON