Skip to main content
Mallory
HighVulnerability

CVE-2026-3081: GStreamer H.266 pic_timing SEI Stack Buffer Overflow

Published Mar 13, 2026 · Updated 2 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.51%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gstreamer
IdentifiersCVE-2026-3081CWE-121 · Stack-based Buffer Overflow

CVE-2026-3081 is a stack-based buffer overflow in the GStreamer H.266 video bitstream parser within gst-plugins-bad. While processing decoding units in picture-timing supplemental enhancement information (pic_timing SEI) messages, the parser insufficiently validates attacker-controlled lengths before copying data into a fixed-size stack buffer. A crafted H.266 input can corrupt stack memory, crash the consuming application, and potentially execute arbitrary code in its process context. The affected upstream version range is gst-plugins-bad 1.25.1 through versions before 1.28.1, excluding releases with backported fixes.

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 malicious H.266 media can cause an application crash or arbitrary code execution with the privileges of the process using GStreamer. Successful code execution can compromise data and resources accessible to that process. Sandboxing may limit the resulting exposure; exploitation does not inherently grant privileges beyond the affected process.

Mitigation

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

Until patched, prevent affected applications from processing untrusted H.266 media. Where GNOME localsearch or tracker-miners automatically extracts media metadata, disabling extraction rules can reduce exposure through background indexing but does not protect other GStreamer consumers. Sandbox isolation can limit exploitation impact but does not correct the overflow. No parser-specific alternative workaround is documented.

Remediation

Patch, then assume compromise.

Upgrade gst-plugins-bad to version 1.28.1 or a later supported release, or install a distribution package containing the fix. The fix was also included in the legacy 1.26.11 release, although the 1.26 branch is no longer actively maintained. Alternatively, apply the upstream patch and rebuild the affected component. For NewStart CGSL MAIN 7.02, obtain corrected gstreamer1 packages from ZTE; availability must be confirmed with the vendor.

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-3081 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-3081 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3081?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-3081.
Is there a patch for CVE-2026-3081?
Upgrade gst-plugins-bad to version 1.28.1 or a later supported release, or install a distribution package containing the fix. The fix was also included in the legacy 1.26.11 release, although the 1.26 branch is no longer actively maintained.
What products are affected by CVE-2026-3081?
Gstreamer.
How severe is CVE-2026-3081?
CVE-2026-3081 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.51% (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.