CVE-2026-125707 · Package
NO FIX YET
GStreamer's MXF demuxer has an off-by-one bounds check that lets a crafted MXF media file write one byte past the end of an array. The write can corrupt memory and crash the application that opens the file.
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 GStreamer to parse MXF files, such as media players, transcoders and ingest pipelines, are exposed when they process untrusted MXF input. Applications that never open MXF files from outside sources can skip it. The sources do not give affected versions.
Not affected if no-untrusted-mxf-input
Who cares gstreamer, media-processing, mxf
Unknown from the sources.
No fix yet, per the sources.
A flaw was found in GStreamer's MXF demuxer. When an application processes a crafted MXF file, an off-by-one bounds check can allow a one-byte write past the logical end of a temporal offset array. This may corrupt memory and cause the application to crash. The extent of the impact has not been demonstrated by a runtime test.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/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.