CVE-2026-44041: Out-of-bounds Read in uvnc UltraVNC
UltraVNC through 1.8.2.2 contains an out-of-bounds read in the wide-string to multibyte conversion helper. In rfb/dh.cpp:204, the vncWc2Mb() function passes a caller-supplied WCHAR pointer to wcslen() before any bounds check. If the caller provides a wide-character buffer that is not properly NUL-terminated, wcslen() reads past the end of the buffer until it encounters a NUL wchar, resulting in an out-of-bounds read. Under typical Win32 API usage this requires an abnormal caller contract. Impact is limited to a potential information disclosure from adjacent memory regions or a process crash (denial of service) if the over-read crosses a page boundary.
AI Analysis
Technical Summary
CVE-2026-44041 is an out-of-bounds read vulnerability in UltraVNC through version 1.8.2.2. The issue arises in the vncWc2Mb() function located in rfb/dh.cpp at line 204, where a caller-supplied WCHAR pointer is passed to wcslen() without bounds checking or ensuring NUL termination. If the input buffer is not properly NUL-terminated, wcslen() reads past the buffer boundary until it finds a NUL wide character, causing an out-of-bounds read. This can result in either a denial of service due to process crash if the read crosses a page boundary or limited information disclosure from adjacent memory. The vulnerability requires an abnormal caller contract uncommon in typical Win32 API usage. There is no vendor advisory or patch information available at this time.
Potential Impact
The vulnerability can lead to a denial of service via process crash if the out-of-bounds read crosses a memory page boundary. Additionally, there is a potential for limited information disclosure from adjacent memory regions. There is no indication of privilege escalation, code execution, or broader impact. Exploitation requires abnormal input conditions that are not typical in normal usage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid supplying or processing improperly NUL-terminated wide-character buffers in the affected function. No official mitigation or workaround has been published.
CVE-2026-44041: Out-of-bounds Read in uvnc UltraVNC
Description
UltraVNC through 1.8.2.2 contains an out-of-bounds read in the wide-string to multibyte conversion helper. In rfb/dh.cpp:204, the vncWc2Mb() function passes a caller-supplied WCHAR pointer to wcslen() before any bounds check. If the caller provides a wide-character buffer that is not properly NUL-terminated, wcslen() reads past the end of the buffer until it encounters a NUL wchar, resulting in an out-of-bounds read. Under typical Win32 API usage this requires an abnormal caller contract. Impact is limited to a potential information disclosure from adjacent memory regions or a process crash (denial of service) if the over-read crosses a page boundary.
CVSS v3.1
Score 4.3medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44041 is an out-of-bounds read vulnerability in UltraVNC through version 1.8.2.2. The issue arises in the vncWc2Mb() function located in rfb/dh.cpp at line 204, where a caller-supplied WCHAR pointer is passed to wcslen() without bounds checking or ensuring NUL termination. If the input buffer is not properly NUL-terminated, wcslen() reads past the buffer boundary until it finds a NUL wide character, causing an out-of-bounds read. This can result in either a denial of service due to process crash if the read crosses a page boundary or limited information disclosure from adjacent memory. The vulnerability requires an abnormal caller contract uncommon in typical Win32 API usage. There is no vendor advisory or patch information available at this time.
Potential Impact
The vulnerability can lead to a denial of service via process crash if the out-of-bounds read crosses a memory page boundary. Additionally, there is a potential for limited information disclosure from adjacent memory regions. There is no indication of privilege escalation, code execution, or broader impact. Exploitation requires abnormal input conditions that are not typical in normal usage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid supplying or processing improperly NUL-terminated wide-character buffers in the affected function. No official mitigation or workaround has been published.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- securin
- Date Reserved
- 2026-05-05T03:40:37.003Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a44a07827e9c79719fbd5bd
Added to database: 07/01/2026, 05:07:04 UTC
Last enriched: 07/01/2026, 05:22:48 UTC
Last updated: 07/01/2026, 23:38:12 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.