FFmpeg Heap Buffer Overflow Vulnerability: Early Warning
- Severity
- CRITICAL
- CVSS
- 9.8
- Affected component
- ffmpeg (other)
- Patched version
- 1c10bcc
An early warning has been issued for a critical heap buffer overflow vulnerability in FFmpeg before commit 1c10bcc. This vulnerability can be triggered by a remote RIST sender sending a packet with a payload exceeding the caller buffer size.
What happened
FFmpeg before commit 1c10bcc reportedly contains a heap buffer overflow in the RIST protocol reader. This vulnerability can be triggered by a remote RIST sender sending a packet with a payload exceeding the caller buffer size. The vulnerability is under investigation and has been assigned the identifier CVE-2026-75143 with a CVSS score of 9.8, indicating a critical severity level.
To assess your exposure, check if your FFmpeg installation is before commit 1c10bcc. If so, you are potentially vulnerable to this heap buffer overflow. It is recommended to upgrade to commit 1c10bcc or later to mitigate the risk.
What to do about it
- Upgrade FFmpeg to commit 1c10bcc or later to mitigate the risk of this vulnerability.
- Check your FFmpeg installation to ensure it is at or after commit 1c10bcc.
- Monitor the primary sources for updates on this vulnerability.
- Consider implementing additional security measures to protect against potential exploitation of this vulnerability.
How 0Day would have caught this
ffmpeg is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are potentially affected if your FFmpeg installation is before commit 1c10bcc.
What should I do right now?
Upgrade FFmpeg to commit 1c10bcc or later to mitigate the risk of this vulnerability.
Has this been exploited in the wild?
There is no confirmed report of this vulnerability being exploited in the wild at this time.
Where can I find more information?
Consult the primary sources, including the NVD page for CVE-2026-75143, for more detailed information.