GST-PLUGINS-BAD · CVE-2026-125703 · Package
NO FIX YET
The GStreamer gst-plugins-bad MXF plugin does not check bounds when parsing VANC ancillary data, causing out-of-bounds reads and writes. Processing a crafted MXF file may crash the application, a denial of service.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that use the GStreamer gst-plugins-bad MXF demuxer or muxer to process MXF media files, especially ones that accept untrusted uploads. Systems that never parse MXF content are not exposed. The sources do not name affected versions.
Not affected if no-mxf-processing
Who cares gstreamer, media-processing, mxf
Unknown from the sources.
No fix yet, per the sources.
A flaw was found in the GStreamer gst-plugins-bad MXF plugin. Insufficient bounds checks when parsing crafted VANC data can cause an out-of-bounds read in the demuxer, while an incorrect buffer size calculation when muxing multiple ancillary packets can cause an out-of-bounds write. Processing affected content may crash the application, resulting in a denial of service.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.