High [CVE-2026-75143] FFmpeg Heap Buffer Overflow via RIST Protocol Reader
This high-severity Red Hat Linux advisory covers CVE-2026-75143.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
FFmpeg before commit 1c10bcc contains a heap buffer overflow in the RIST protocol reader (libavformat/librist.c). librist_read() ignored its size argument and copied the full received payload length into the caller-provided destination buffer, overflowing it when the payload exceeds the destination size.
This is reachable via the async:rist:// URL scheme, where the async wrapper supplies a smaller buffer than the received payload. A remote RIST sender can trigger the overflow by sending a packet whose payload exceeds the caller buffer size.
A flaw was found in FFmpeg. A heap buffer overflow in the RIST protocol reader allows a remote attacker to trigger memory corruption by sending an oversized packet to an FFmpeg instance receiving a RIST stream.
This could lead to denial of service or arbitrary code execution. The ffmpeg package is not shipped in base Red Hat Enterprise Linux.
It is available through EPEL and Fedora with librist support enabled. Red Hat OpenShift AI container images do not directly install FFmpeg.
Exploitation requires the victim to be actively receiving a RIST stream, which is a niche broadcast video protocol not used in typical RH product deployments. Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Weakness: CWE-120.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Mitigation checklist
- No mitigation is currently available for this flaw.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.