CVEvulnerability
CVE-2026-44040
6.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2026-07-01
- Last modified
- 2026-10-25
- Assigner
- 33c584b5-0579-4c06-b2a0-8d8329fcab9c
- CVSS 3.1 (33c584b5-0579-4c06-b2a0-8d8329fcab9c)
- 4.8 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CVSS 3.1 ([email protected])
- 6.5 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- Weaknesses
- CWE-338
Description
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 configurations
• uvnc ultravnc (<= 1.8.2.2)
Related
Weakness · CWE (1)
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) weakness
References
- https://github.com/ultravnc/UltraVNC Product
- https://uvnc.com/ Product, Release Notes
- https://www.securin.io/zero-days/cve-2026-44040-libc-rand-weak-rng-vnc-auth-challenge-ultravnc www.securin.io