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).
CVE-2026-7838
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 63.1%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 2, 2026
Advisory Details (2)
Auto-updated Jul 1, 2026GitHub - ultravnc/UltraVNC: 👁️ UltraVNC Server, UltraVNC Viewer, UltraVNC Repeater and UltraVNC SC | Official repository: https://github.com/ultravnc/UltraVNC · GitHub
https://github.com/ultravnc/UltraVNCVendor Advisories for CVE-2026-7838(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 35× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 06:20 UTCEG score recompute
- 2026-07-07 06:20 UTCGHSA enrichment
- 2026-07-06 18:16 UTCEG score recompute
- 2026-07-06 18:16 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 06:11 UTCEG score recompute
- 2026-07-06 06:11 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 18:02 UTCEG score recompute
- 2026-07-05 18:02 UTCGHSA enrichment
- 2026-07-05 05:58 UTCEG score recompute
- 2026-07-05 05:58 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 17:54 UTCEG score recompute
- 2026-07-04 17:54 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 05:49 UTCEG score recompute
- 2026-07-04 05:48 UTCGHSA enrichment
- 2026-07-03 17:41 UTCEG score recompute
- 2026-07-03 17:41 UTCGHSA enrichment
- 2026-07-03 05:37 UTCEG score recompute
Show 10 moreShow fewer
- 2026-07-03 05:37 UTCGHSA enrichment
- 2026-07-02 17:33 UTCEG score recompute
- 2026-07-02 17:32 UTCGHSA enrichment
- 2026-07-02 05:28 UTCEG score recompute
- 2026-07-02 05:28 UTCGHSA enrichment
- 2026-07-01 17:24 UTCEG score recompute
- 2026-07-01 17:24 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 05:21 UTCEG score recompute
- 2026-07-01 05:20 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-787
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(5)
What is CVE-2026-7838?
When was CVE-2026-7838 disclosed?
Is CVE-2026-7838 actively exploited?
What is the CVSS score of CVE-2026-7838?
How do I remediate CVE-2026-7838?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-7838
Is Your Infrastructure Affected by CVE-2026-7838?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.