dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-52722

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A signed integer overflow vulnerability was found in GStreamer's VMnc decoder. A crafted VMnc stream with large cursor dimensions can overflow signed integer payload-size arithmetic, bypassing a length check and leading to out-of-bounds reads. A remote attacker could trick a user into opening a specially crafted VMnc file, potentially causing a crash or information disclosure.

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

A signed integer overflow exists in GStreamer's VMnc decoder where large cursor dimensions in a crafted VMnc stream cause overflow in signed integer payload-size arithmetic. This overflow bypasses a length check, enabling out-of-bounds memory reads. A remote attacker can exploit this by tricking a user into opening a malicious VMnc file, potentially causing denial of service or information disclosure.

MitigationApply available patches for GStreamer to fix the integer overflow in the VMnc decoder. Until a patch is available, avoid opening untrusted VMnc files from unknown sources.

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

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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. Identify GStreamer installation and version
    Run `gst-inspect-1.0 --version` or check your system's package manager for the GStreamer package version (e.g., `dpkg -l | grep gstreamer` or `rpm -qa | grep gstreamer`).
    Affected if The installed version is older than the patched version containing the fix for CVE-2026-52722.
  2. Verify VMnc decoder plugin availability
    Run `gst-inspect-1.0 vmnc` or list all available decoders with `gst-inspect-1.0 -a | grep -i vmnc` to confirm the VMnc plugin is installed.
    Affected if The VMnc decoder plugin is present and loadable in your GStreamer installation.
  3. Confirm VMnc file handling capability
    Check if applications in your environment can process VMnc files by inspecting file associations or testing with a sample VMnc file using a media player built on GStreamer (e.g., `gst-play-1.0 <file.vmnc`).
    Affected if Your system can decode VMnc streams, enabling the vulnerable code path.
  4. Review application logs for VMnc processing
    Examine application and system logs for any instances where VMnc files were opened or decoded, particularly with unusual cursor data.
    Affected if VMnc files have been processed, indicating the affected code path was exercised.

You are affected if GStreamer with a VMnc decoder plugin is installed and processes untrusted VMnc files without the CVE-2026-52722 patch applied.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available patches for GStreamer to fix the integer overflow in the VMnc decoder. Until a patch is available, avoid opening untrusted VMnc files from unknown sources.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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