CVE-2026-125707: gstreamer1-plugins-bad-free security update
Affects gstreamer1-plugins-bad-freeSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 1.22.12-15.el9_9 soon.
Data as of 20 Nov 2026, 14:06 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 1.22.12-15.el9_9
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 19 Nov 2026.
What to do
Upgrade the AlmaLinux to 1.22.12-15.el9_9.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlmaLinux 9gstreamer1-plugins-bad-free | Affected
| Fixed in
|
| AlmaLinux 9gstreamer1-plugins-bad-free-devel | Affected
| Fixed in
|
| AlmaLinux 9gstreamer1-plugins-bad-free-libs | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official security update provided by Red Hat by upgrading to gstreamer1-plugins-bad-free version 1.22.12-15.el9_9 or later. This update addresses the off-by-one write vulnerability. No additional mitigation steps are indicated by the vendor.
Description
A moderate severity security vulnerability (CVE-2026-125707) exists in the gstreamer1-plugins-bad-free package, specifically an off-by-one write flaw in the MXF demuxer temporal offset table. This vulnerability affects versions prior to 1.22.12-15.el9_9. A fixed version is available in 1.22.12-15.el9_9. The issue was addressed by Red Hat in an official security advisory.