LibVNCServer versions 0.9.15 and prior (fixed in commit 009008e) contain a heap out-of-bounds read vulnerability in the UltraZip encoding handler that allows a malicious VNC server to cause information disclosure or application crash. Attackers can exploit improper bounds checking in the HandleUltraZipBPP() function by manipulating subrectangle header counts to read beyond the allocated heap buffer.
Security readout for executives and security teams
Plain-English summary
This flaw lets a malicious VNC server make software using vulnerable LibVNCServer read past a heap buffer. The likely outcomes are limited information disclosure or an application crash, not code execution based on the supplied sources. It is remotely reachable and needs no authentication, so internet-facing or automated VNC workflows should be reviewed promptly.
Executive priority
Treat this as a moderate-priority patch and inventory task. It can be triggered remotely and may crash affected software, but current supplied evidence points to limited confidentiality and availability impact with no confirmed active exploitation.
Technical view
CVE-2026-32853 is a CWE-125 heap out-of-bounds read in LibVNCServer 0.9.15 and prior. The issue is in HandleUltraZipBPP(), where manipulated UltraZip subrectangle header counts can cause reads beyond the allocated heap buffer. The vulnerability is fixed by commit 009008e2f4d5a54dd71f422070df3af7b3dbc931.
Likely exposure
Exposure is most likely in applications or appliances that embed LibVNCServer 0.9.15 or earlier and process UltraZip-encoded VNC traffic from servers. The supplied sources do not identify specific downstream products, distributions, or vulnerable packaged versions.
Exploitation context
The CVSS vector indicates network attack, low complexity, no privileges, and no user interaction. The provided KEV flag is false, and the supplied sources do not state active exploitation or public weaponized exploitation.
Researcher notes
Key unknowns are downstream exposure and packaged fixed versions. Focus validation on embedded LibVNCServer copies, UltraZip handling reachability, and whether the fix commit is present. Do not infer broader product impact from the library advisory alone.
Mitigation direction
Upgrade to a release or package containing commit 009008e2f4d5a54dd71f422070df3af7b3dbc931.
If no packaged fix exists, check LibVNC and distribution guidance before applying source patches.
Restrict VNC connectivity to trusted servers and networks until patched.
Inventory products that bundle LibVNCServer rather than only checking direct dependencies.
Validation and detection
Identify whether LibVNCServer is present and determine the exact embedded or packaged version.
Confirm whether the deployed code includes commit 009008e2f4d5a54dd71f422070df3af7b3dbc931.
Review SBOMs and vendor notices for appliances or applications using LibVNCServer.
Check crash logs for VNC or UltraZip-related failures, without assuming exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.