Skip to main content
Mallory
HighVulnerability

CVE-2026-2920: GStreamer ASF Demuxer Heap Buffer Overflow and Remote Code Execution

Published Mar 13, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.91%61st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gstreamer
IdentifiersCVE-2026-2920CWE-122 · Heap-based Buffer Overflow

CVE-2026-2920 affects the ASF demuxer in GStreamer's gst-plugins-ugly package. Insufficient validation of attacker-controlled lengths during ASF stream-header processing allows data to be copied beyond a fixed-length heap buffer, causing memory corruption and potentially arbitrary code execution in the consuming process. The original out-of-bounds write affects versions before 1.28.1. A follow-up advisory under the same CVE identifies out-of-bounds reads in versions before 1.28.5: insufficient validation of replicated-data lengths and cumulative payload-extension offsets permits reads beyond a fixed 256-byte buffer, and the TIMING extension reads eight bytes without verifying that sufficient data remains.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Processing a malicious ASF file can corrupt heap memory, crash the consuming application, or permit arbitrary code execution with that application's privileges. Successful code execution can compromise data and resources accessible to the process. The related out-of-bounds reads addressed by the follow-up advisory can cause denial of service or information disclosure when processing crafted ASF or WMV media.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary workaround is specified. Until patched, prevent untrusted ASF and WMV media from reaching applications that use the affected demuxer. Where GNOME localsearch or tracker-miners automatically extracts media metadata, disabling the relevant extraction rules reduces exposure to automatic parsing. Sandboxing the consuming process can limit exploitation impact but does not correct the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade gst-plugins-ugly to version 1.28.5 or a later supported release containing both the original and follow-up fixes. Version 1.28.1 fixes the original out-of-bounds write but does not address the follow-up out-of-bounds reads. For older branches, install vendor-provided security updates or apply the corresponding upstream patches and rebuild. Ubuntu systems should install the corrected gstreamer1.0-plugins-ugly package for their release; availability may depend on Ubuntu Pro ESM Apps.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GstreamerGstreamerapplication
FAQ

Frequently asked questions

Is CVE-2026-2920 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-2920 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-2920?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-2920.
Is there a patch for CVE-2026-2920?
Upgrade gst-plugins-ugly to version 1.28.5 or a later supported release containing both the original and follow-up fixes. Version 1.28.1 fixes the original out-of-bounds write but does not address the follow-up out-of-bounds reads.
What products are affected by CVE-2026-2920?
Gstreamer.
How severe is CVE-2026-2920?
CVE-2026-2920 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.91% (61st percentile) as of Nov 19, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.