dbcve.org
TigervncApplication

CVE-2026-34352

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 1.16.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
In TigerVNC before 1.16.2, Image.cxx in x0vncserver allows other users to observe or manipulate the screen contents, or cause an application crash, because of incorrect permissions.

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 · moderate confidence

TigerVNC before version 1.16.2 contains a permission vulnerability in Image.cxx within the x0vncserver component. The incorrect permissions on shared memory or framebuffer resources allow other local users to observe screen contents (information disclosure), manipulate screen content (data modification), or cause the application to crash (denial of service).

MitigationUpgrade to TigerVNC version 1.16.2 or later which contains the corrected permission handling in x0vncserver.

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
TigervncApplication
Affected:< 1.16.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm TigerVNC installation
    Run 'vncserver --version' or 'vncviewer --version' to check if TigerVNC is installed on the system
    Affected if No TigerVNC binary is found or the command fails
  2. Identify installed TigerVNC version
    Execute the version command from the previous step and compare the output to 1.16.2. Look for version strings like 'TigerVNC 1.x.y' where x.y is less than 16.2
    Affected if The installed version is before 1.16.2 (for example, 1.15.0, 1.14.1, etc.)
  3. Verify x0vncserver component presence
    Check if the x0vncserver binary exists on the system using 'which x0vncserver' or by listing /usr/bin/x0vncserver or similar paths
    Affected if The x0vncserver binary is present and the TigerVNC version is below 1.16.2
  4. Determine if x0vncserver is actively running
    Check running processes with 'ps aux | grep x0vncserver' or review any systemd service files or startup scripts that reference x0vncserver
    Affected if x0vncserver is currently running or configured to run, combined with a vulnerable version
  5. Inspect shared memory/framebuffer resource permissions
    Use 'ipcs -m' to list shared memory segments while x0vncserver is running, and check file permissions on /tmp/.X11-unix or similar X11 socket directories if applicable
    Affected if Resources used by x0vncserver show overly permissive access (world-readable or world-writable) that would allow other local users to access them

The environment is affected if TigerVNC version 1.16.2 or later is NOT installed AND the x0vncserver component is in use or planned for use.

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.16.2 or later
Fixed in 1.16.2
Vendor patch github.com →
Interim mitigation

Upgrade to TigerVNC version 1.16.2 or later which contains the corrected permission handling in x0vncserver.

Recommended fix High confidence

1.16.2

  1. Check current installed version of TigerVNC (e.g., `vncserver -version` or check package manager)
  2. Upgrade TigerVNC to version 1.16.2 or later using your distribution's package manager (e.g., `apt update && apt install tigervnc` on Debian/Ubuntu, `yum update tigervnc` on RHEL/CentOS, or compile from source)
  3. Verify the upgrade was successful by checking the version: `vncserver -version` or `x0vncserver -version`
  4. Restart any running VNC server instances to ensure the patched version is in use

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

Fix this in Tigervnc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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