CVE-2026-18295 is an out-of-bounds write vulnerability in GStreamer MRF file parsing. Insufficient validation of attacker-controlled MRF file data can cause a write beyond the end of an allocated buffer. An attacker can craft malicious media content that, when processed by an affected GStreamer installation, may enable arbitrary code execution in the current process context. The issue affects GStreamer good-plugin packages, including associated GTK components, on supported distributions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by Miracle Linux advisory AXSA-2026-1677 affecting the listed GStreamer Good plugin packages on Miracle Linux 8.
A vulnerability addressed by AlmaLinux advisory ALSA-2026:59152 for GStreamer good GTK plugin packages on AlmaLinux 9. The content does not provide a vulnerability-specific technical description.
A GStreamer remote-code-execution vulnerability triggered through parsing an MRF file.
A GStreamer flaw in MRF file parsing that can enable remote code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.