dbcve.org
Debian LinuxOperating system · Debian

CVE-2026-1940

HIGH · 7.5 CVSS v3.1 Published 2026-03-23
Fix available
A fix is available. Upgrade to 1.28.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An incomplete fix for CVE-2024-47778 allows an out-of-bounds read in gst_wavparse_adtl_chunk() function. The patch added a size validation check lsize + 8 > size, but it does not account for the GST_ROUND_UP_2(lsize) used in the actual offset calculation. When lsize is an odd number, the parser advances more bytes than validated, causing OOB read.

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

An incomplete fix for CVE-2024-47778 in GStreamer's wavparse plugin allows out-of-bounds read. The patch added validation check 'lsize + 8 > size' but fails to account for GST_ROUND_UP_2(lsize) used in actual offset calculation - when lsize is odd, the parser advances more bytes than validated, causing OOB read.

MitigationApply a complete fix that validates size against GST_ROUND_UP_2(lsize) + 8 instead of lsize + 8, ensuring the validation matches the actual memory advancement. Test with WAV files containing odd-sized adtl chunks.

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
Debian LinuxOperating system
Affected:= 11.0= 12.0
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0= 10.0
Gst Plugins GoodPlugin / extension
Affected:= 1.0.0
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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check GStreamer core library version
    Run 'gst-inspect-1.0 --version' or check the installed libgstreamer-1.0 package version via package manager (dpkg -l libgstreamer-1.0-0 or rpm -q gstreamer)
    Affected if The installed version is less than 1.28.1 (e.g., 1.26.x, 1.24.x, etc.)
  2. Check GStreamer Good Plugins package version
    Check the installed gst-plugins-good package version via package manager (dpkg -l gst-plugins-good-1.0 or rpm -q gst-plugins-good)
    Affected if The installed version is 1.0.0 or lower and the GStreamer core is also below 1.28.1
  3. Verify wavparse plugin availability
    Run 'gst-inspect-1.0 wavparse' to confirm the plugin is installed and inspectable
    Affected if The plugin is present and the GStreamer version is in the affected range (below 1.28.1)
  4. Confirm WAV file parsing is in use
    Inspect any media pipelines or applications that process WAV files using GStreamer (check for 'wavparse' element in gst-launch pipelines, application code, or container configurations)
    Affected if WAV files are being parsed by the affected wavparse plugin in the GStreamer pipeline

You are affected if GStreamer core library or gst-plugins-good version is below 1.28.1 and your application/pipeline uses the wavparse element to process WAV files.

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 a complete fix that validates size against GST_ROUND_UP_2(lsize) + 8 instead of lsize + 8, ensuring the validation matches the actual memory advancement. Test with WAV files containing odd-sized adtl chunks.

Recommended fix High confidence

Gstreamer 1.28.1 or later (or vendor-supplied patch for 1.28 series)

  1. 1. Identify the current GStreamer installation version using: rpm -qa | grep gstreamer (RHEL) or dpkg -l | grep gstreamer (Debian)
  2. 2. For Debian 11/12: Run apt-get update && apt-get install libgstreamer1.0-0 gstreamer1.0-plugins-good to get the latest available version
  3. 3. For RHEL/CentOS/Enterprise Linux 7-10: Run yum update gstreamer1 gstreamer1-plugins-good or dnf update gstreamer1 gstreamer1-plugins-good
  4. 4. Verify the installed version meets or exceeds 1.28.1 using: gst-inspect-1.0 --version or rpm -qa | grep gstreamer1
  5. 5. Restart any applications using GStreamer to ensure the updated libraries are loaded
Caveat Minor: Some legacy WAV parsing edge cases may behave differently; plugin API remains compatible

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1940 — 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-1940 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