Skip to main content
Mallory
HighVulnerability

CVE-2026-3084: Integer Underflow and Code Execution in GStreamer H.266 Parser

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.50%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gstreamer
IdentifiersCVE-2026-3084CWE-191 · Integer Underflow (Wrap or…

CVE-2026-3084 is an integer underflow vulnerability in the H.266 video bitstream parser in GStreamer gst-plugins-bad. Insufficient validation of attacker-controlled picture-partition data can cause an integer underflow before a memory write, resulting in an out-of-bounds write. The vulnerability affects versions from 1.25.1 through versions preceding 1.28.1, subject to maintenance-branch fixes. Crafted media can crash the consuming application or potentially execute arbitrary code in its process context.

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.

Successful exploitation can corrupt memory, terminate the application processing the media, or potentially execute arbitrary code with that application's privileges. Code execution could compromise data and resources accessible to the affected process. The practical impact depends on the application's privileges and sandbox restrictions.

Mitigation

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

No separate vendor-specified temporary workaround is documented. Until patched, prevent affected applications from processing untrusted H.266 media. Where automatic media metadata extraction invokes the affected parser, disabling extraction can reduce exposure. Sandboxing media-processing applications can limit exploitation impact but does not correct the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade gst-plugins-bad to version 1.28.1 or a later fixed release. GStreamer 1.26.11 also includes the H.266 parser security fixes, although the 1.26 branch is no longer actively maintained. For deployments that cannot upgrade, apply the upstream patch for GStreamer-SA-2026-0011 and rebuild the affected component.

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-3084 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-3084 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3084?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-3084.
Is there a patch for CVE-2026-3084?
Upgrade gst-plugins-bad to version 1.28.1 or a later fixed release. GStreamer 1.26.11 also includes the H.266 parser security fixes, although the 1.26 branch is no longer actively maintained.
What products are affected by CVE-2026-3084?
Gstreamer.
How severe is CVE-2026-3084?
CVE-2026-3084 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.50% (44th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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.