CVE-2026-12893: Memory Leak and NULL Pointer Dereference in gst-libav Demuxer
CVE-2026-12893 affects the gst-libav demuxer in versions before 1.28.4. Error-handling paths during media-source opening fail to free the I/O context and may dereference a NULL format-context pointer. Corrupted or specially crafted media can trigger application crashes, while repeated failed opening attempts can leak memory.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Applications using the affected demuxer can suffer denial of service through a NULL pointer dereference. Repeated failed media-source opening attempts can also exhaust resources through accumulated memory leaks.
Remediation
Patch, then assume compromise.
Upgrade gst-libav to version 1.28.4 or later. Users maintaining older GStreamer versions should apply the provided security patch and recompile.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-12893 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-12893 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-12893?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-12893.
- Is there a patch for CVE-2026-12893?
- Upgrade gst-libav to version 1.28.4 or later. Users maintaining older GStreamer versions should apply the provided security patch and recompile.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.