Skip to main content
VulnerabilityPublished

CVE-2026-125707: GStreamer's MXF demuxer · Out-of-bounds Write

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-125707· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade Red Hat Enterprise Linux 10 to 1.28.3 when convenient.

Data as of 10 Nov 2026, 15:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.16.1
Patch
Available – fixed in 1.28.3
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade gst-plugins-bad to 1.28.3.

Affected software

ProductAffectedFixed in
GStreamergst-plugins-badAffected
  • <1.28.3
Fixed in
  • 1.28.3

AI-suggested

Red Hat has deferred fixes under their moderate severity policy for affected product streams through RHEL 10.3. Mitigation is possible by setting the environment variable GST_PLUGIN_FEATURE_RANK=mxfdemux:NONE before launching GStreamer applications to prevent automatic selection of the vulnerable mxfdemux plugin. This mitigation does not protect pipelines that explicitly instantiate mxfdemux. Users should apply vendor patches when available and consider disabling MXF processing if not needed.

Description

CVE-2026-125707 is a moderate severity vulnerability in GStreamer's MXF demuxer where processing a crafted MXF file can cause an off-by-one out-of-bounds write past the end of a temporal offset array. This memory corruption may lead to application crashes. The vulnerability requires local processing of a malicious file and user interaction. No confirmed exploitation or code execution has been demonstrated.

References

Community reviews

Loading reviews…