dbcve.org
GstreamerApplication

CVE-2026-3082

HIGH · 7.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.28.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GStreamer JPEG Parser Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the processing of Huffman tables. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28840.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in GStreamer's JPEG parser during Huffman table processing. The vulnerability results from missing length validation before copying user-supplied data to a fixed-size heap buffer, allowing remote code execution in the context of the current process.

MitigationApply vendor patches for GStreamer when available. Until then, validate all JPEG inputs before processing and consider sandboxing media parsing components to limit exploitation impact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GstreamerApplication
Affected:< 1.28.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GStreamer installation and version
    Run 'gst-inspect-1.0 --version' or check your system's package manager for gstreamer version (dpkg -l | grep gstreamer, rpm -qa | grep gstreamer, or brew list --versions gstreamer)
    Affected if Installed version is lower than 1.28.1
  2. Confirm JPEG parsing component is present
    Run 'gst-inspect-1.0 jpegdec' or 'gst-inspect-1.0 jpegparse' to verify the JPEG decoder/parser plugin is available
    Affected if The jpegdec or jpegparse plugin is installed and loadable
  3. Verify Huffman table processing is in use
    Inspect any media pipelines or applications that process JPEG files through GStreamer (check for files like .mp4, .avi, .mov that contain JPEG streams, or direct JPEG image loading)
    Affected if GStreamer is actively parsing JPEG files containing Huffman table data
  4. Check for untrusted JPEG input sources
    Review logs or network sources that feed JPEG content to GStreamer-based applications (surveillance feeds, media servers, file upload processing)
    Affected if GStreamer processes JPEG from untrusted or network-based sources

You are affected if GStreamer version is below 1.28.1 and the system parses JPEG files through GStreamer's Huffman table processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.28.1 or later
Fixed in 1.28.1
Interim mitigation

Apply vendor patches for GStreamer when available. Until then, validate all JPEG inputs before processing and consider sandboxing media parsing components to limit exploitation impact.

Recommended fix High confidence

GStreamer 1.28.1 or later

  1. 1. Identify the current GStreamer version installed on the system using your package manager (e.g., `gst-inspect-1.0 --version` or checking via apt/yum/dnf).
  2. 2. Update the GStreamer packages to version 1.28.1 or later using the system's package manager (e.g., `sudo apt update && sudo apt install libgstreamer1.0-dev gstreamer1.0-plugins-*` or equivalent).
  3. 3. Verify the installed version meets the minimum fixed version requirement (1.28.1 or newer).
  4. 4. Restart any applications or services that use GStreamer to ensure the updated libraries are loaded.
Caveat Review release notes for intermediate versions between current and 1.28.1 for any plugin or API compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gstreamer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3082 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data