Skip to main content
Mallory
HighVulnerability

CVE-2026-3082: Heap-Based Buffer Overflow in GStreamer JPEG 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.95%62nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gstreamer
IdentifiersCVE-2026-3082CWE-122 · Heap-based Buffer Overflow

CVE-2026-3082 is a heap-based buffer overflow in the JPEG parser in GStreamer gst-plugins-bad before version 1.28.1. During Huffman table processing, insufficient validation of attacker-controlled data lengths allows data to be copied beyond a fixed-length heap buffer. Processing a specially crafted JPEG can crash the consuming application or enable arbitrary code execution in the context of that process. The vulnerability is also tracked as ZDI-CAN-28840 and GStreamer-SA-2026-0003.

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 compromise the confidentiality, integrity, and availability of the application processing the malicious JPEG, allowing arbitrary code execution with the application's privileges. Heap corruption can also cause application crashes and denial of service. Any sandbox restrictions on the consuming process constrain the immediate impact; the vulnerability does not itself establish a sandbox escape or privilege escalation.

Mitigation

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

Until patched, avoid processing JPEG files from untrusted sources and disable affected processing paths where feasible. The upstream advisory identifies disabling the VA plugin and removing the parse-jpeg example, or avoiding the VA JPEG decoder, encoder, and parsing example, as alternatives. Where automatic metadata extraction exposes untrusted files to GStreamer, disabling the relevant extraction rules can reduce exposure. Sandboxing consuming applications can limit the consequences of exploitation but does not correct the overflow.

Remediation

Patch, then assume compromise.

Upgrade gst-plugins-bad to version 1.28.1 or a later supported release containing the fix. Security fixes are also available in the older 1.26.11 release, although the 1.26 branch is no longer actively maintained. For older branches, apply the upstream bounds-checking patch and rebuild, or install the corresponding distribution security updates.

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-3082 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-3082 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3082?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-3082.
Is there a patch for CVE-2026-3082?
Upgrade gst-plugins-bad to version 1.28.1 or a later supported release containing the fix. Security fixes are also available in the older 1.26.11 release, although the 1.26 branch is no longer actively maintained.
What products are affected by CVE-2026-3082?
Gstreamer.
How severe is CVE-2026-3082?
CVE-2026-3082 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.95% (62nd 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 activity6Community discussion across Reddit, Mastodon, and other social sources.