Quick answers
- Is CVE-2026-18295 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18295 being exploited in the wild.
- How severe is CVE-2026-18295?
- High severity, with a CVSS score of 7.8, published 20 August 2026.
- Which products and versions are affected?
- GStreamer gst-plugins-good < 1.28.5.
- Is there a fix for CVE-2026-18295?
- A patch was published on 2026-08-20: GStreamer 1.28.5 release published Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18295 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-18295?
- Check whether you run Gstreamer. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap buffer overflow exists in the qtmoovrecover element (MOV/MP4 moov recovery tool) within gst-plugins-good when parsing recovery files. The vulnerability stems from insufficient validation of atom size fields in MRF files; the parser trusts declared atom sizes without checking minimum expected sizes, leading to undersized heap buffer allocations. When subsequent atom field writes occur, they overflow past the allocation boundary. Exploitation requires user interaction (opening a malicious .MRF file) and invocation of the qtmoovrecover utility, limiting exposure. An attacker can achieve heap corruption, denial of service, or arbitrary code execution. GStreamer 1.28.5 and later versions include fixes that validate box sizes during parsing.
Affected products
- GStreamer gst-plugins-good < 1.28.5
Timeline
- 2026-05-20: disclosed: Vulnerability reported to vendor
- 2026-07-29: advisory: Coordinated public release of advisory
- 2026-08-20: patched: GStreamer 1.28.5 release published