Description
UltraVNC viewer through 1.8.2.2 contains an integer overflow leading to a heap buffer overflow in the RFB protocol failure-response parsing path. In vncviewer/ClientConnection.cpp, the 4-byte network-supplied reasonLen field (type CARD32) is passed as reasonLen+1 to CheckBufferSize(). Because both operands are unsigned 32-bit, a reasonLen of 0xFFFFFFFF overflows to 0, causing CheckBufferSize to allocate only 256 bytes. The subsequent ReadString(m_netbuf, reasonLen) call then performs ReadExact for the original 4 GiB length into that 256-byte heap buffer. This overflow is reachable via rfbConnFailed (auth-scheme negotiation) and rfbVncAuthFailed (post-handshake) message types without successful authentication. A malicious VNC server, or any man-in-the-middle on the RFB stream, can trigger this condition when the victim viewer connects, potentially resulting in remote code execution as the user running the viewer. The crash was confirmed with AddressSanitizer on a portable reproduction harness (heap-buffer-overflow WRITE at offset 256).
Published: 2026-07-01
Score: 8.7 High
EPSS: 1.4% Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

UltraVNC viewer 1.8.2.2 contains an integer overflow (CWE-190) in the RFB connection‑f heap-based buffer overflow (CWE-787). The 4‑byte reasonLen value,0xFFFFFFFF by a malicious VNC server or a man‑in, overflows to 0 and causes the client to allocate only 256 bytes. The subsequent read then copies the original 4 GiB reason into that small buffer, allowing arbitrary memory writes on the machine running the viewer. This flaw is reachable before authentication via the rfbConnFailed and rfbVncAuth it a high‑impact remote code execution vector.

Affected Systems

UltraVNC viewer up to and including version 1.8.2.2, to an RFB server over the in the vncviewer/ClientConnection.cpp module that parses RFB failure responses.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. EPSS score of 1% indicates the likelihood of exploitation is low but non‑zero, but the flaw can be triggered without authentication. It is not listed in CISA’s KEV catalog, meaning no reported yet. A client connecting to a overflow, potentially leading to remote code execution on the local user’s system.

Generated by OpenCVE AI on July 21, 2026 at 15:06 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade UltraVNC viewer to a patched version that resolves the integer overflow in RFB failure‑response parsing.
  • If an update is not immediately available, block or filter RFB failure messages with an unusually large reasonLen value (e.g., greater than 256 bytes) using a firewall or the client.
  • Monitor viewer logs and system stability for abnormal crashes or memory corruption patterns that may indicate exploitation attempts.

Generated by OpenCVE AI on July 21, 2026 at 15:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 05:30:00 +0000


Wed, 01 Jul 2026 14:45:00 +0000

Type Values Removed Values Added
First Time appeared Uvnc
Uvnc ultravnc
Vendors & Products Uvnc
Uvnc ultravnc

Wed, 01 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 01 Jul 2026 05:00:00 +0000

Type Values Removed Values Added
Description UltraVNC viewer through 1.8.2.2 contains an integer overflow leading to a heap buffer overflow in the RFB protocol failure-response parsing path. In vncviewer/ClientConnection.cpp, the 4-byte network-supplied reasonLen field (type CARD32) is passed as reasonLen+1 to CheckBufferSize(). Because both operands are unsigned 32-bit, a reasonLen of 0xFFFFFFFF overflows to 0, causing CheckBufferSize to allocate only 256 bytes. The subsequent ReadString(m_netbuf, reasonLen) call then performs ReadExact for the original 4 GiB length into that 256-byte heap buffer. This overflow is reachable via rfbConnFailed (auth-scheme negotiation) and rfbVncAuthFailed (post-handshake) message types without successful authentication. A malicious VNC server, or any man-in-the-middle on the RFB stream, can trigger this condition when the victim viewer connects, potentially resulting in remote code execution as the user running the viewer. The crash was confirmed with AddressSanitizer on a portable reproduction harness (heap-buffer-overflow WRITE at offset 256).
Title UltraVNC viewer heap buffer overflow via integer overflow in RFB connection-failure reason length
Weaknesses CWE-190
CWE-787
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: securin

Published:

Updated: 2026-07-09T04:35:58.564Z

Reserved: 2026-05-05T07:30:55.831Z

Link: CVE-2026-7838

cve-icon Vulnrichment

Updated: 2026-07-01T13:11:36.123Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-21T15:15:08Z

Weaknesses