CVE-2026-44040: UltraVNC vncauth.c uses time-seeded libc rand() to generate VNC authentication challenge bytes
UltraVNC through 1.8.2.2 uses a cryptographically weak pseudo-random number generator to produce VNC authentication challenge bytes. In rfb/vncauth.c:119-129, the vncRandomBytes() function seeds libc rand() with time(0) + getpid() + rand() and generates a 16-byte challenge. The combined seed space is approximately 31 bits (libc rand() internal state) and is entirely determined by publicly-observable values (wall-clock time and process ID). An attacker who can observe the authentication exchange can enumerate the seed space and predict the challenge within seconds, enabling forgery or offline brute-forcing of responses. Note: on Windows, the active code path may use vncEncryptBytes2.cpp which calls CryptGenRandom; reachability on shipped Windows binaries requires compile-graph verification and is under investigation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
UltraVNCto a version that resolves this vulnerability.Fixed in 1.8.2.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44040?
CVE-2026-44040 has a medium severity rating of 6.5.
How do I fix CVE-2026-44040?
To fix CVE-2026-44040, upgrade to the latest version of UltraVNC where the vulnerability has been addressed.
What type of vulnerability is CVE-2026-44040?
CVE-2026-44040 is classified as a weakness in the random number generator used for VNC authentication.
Which versions of UltraVNC are affected by CVE-2026-44040?
All versions of UltraVNC up to 1.8.2.2 are affected by CVE-2026-44040.
What impact does CVE-2026-44040 have on VNC authentication?
CVE-2026-44040 can lead to predictability in VNC authentication challenge bytes, making it easier for an attacker to compromise authentication.