CVE-2026-34352 | TigerVNC up to 1.16.1 x0vncserver Image.cxx permission assignment
VulDBArchived Mar 27, 2026✓ Full text saved
A vulnerability was found in TigerVNC up to 1.16.1 and classified as problematic . This affects an unknown function of the file Image.cxx of the component x0vncserver . Executing a manipulation can lead to incorrect permission assignment. This vulnerability is tracked as CVE-2026-34352 . The attack is restricted to local execution. No exploit exists. It is suggested to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353813 · CVE-2026-34352 · GCVE-0-2026-34352
TIGERVNC UP TO 1.16.1 X0VNCSERVER IMAGE.CXX PERMISSION ASSIGNMENT
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.8 $0-$5k 1.89+
Summaryinfo
A vulnerability was found in TigerVNC up to 1.16.1. It has been classified as problematic. This impacts an unknown function of the file Image.cxx of the component x0vncserver. The manipulation leads to permission assignment. This vulnerability is listed as CVE-2026-34352. The attack must be carried out locally. There is no available exploit. Upgrading the affected component is recommended.
Detailsinfo
A vulnerability was found in TigerVNC up to 1.16.1 and classified as problematic. This issue affects an unknown code block of the file Image.cxx of the component x0vncserver. The manipulation with an unknown input leads to a permission assignment vulnerability. Using CWE to declare the problem leads to CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2026-34352 since 03/26/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 1.16.2 eliminates this vulnerability. Applying the patch 0b5cab169d847789efa54459a87659d3fd484393 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Productinfo
Name
TigerVNC
Version
1.16.0
1.16.1
License
open-source
Website
Product: https://github.com/TigerVNC/tigervnc/
CPE 2.3info
🔒
🔒
CPE 2.2info
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.5
CNA Vector (MITRE): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Permission assignment
CWE: CWE-732 / CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: TigerVNC 1.16.2
Patch: 0b5cab169d847789efa54459a87659d3fd484393
Timelineinfo
03/26/2026 CVE reserved
03/27/2026 +1 days Advisory disclosed
03/27/2026 +0 days VulDB entry created
03/27/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: openwall.com
Status: Confirmed
CVE: CVE-2026-34352 (🔒)
GCVE (CVE): GCVE-0-2026-34352
GCVE (VulDB): GCVE-100-353813
Entryinfo
Created: 03/27/2026 07:25
Changes: 03/27/2026 07:25 (65)
Complete: 🔍
Cache ID: 99:2D0:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸