highCVE-2026-7830

CVE-2026-7830 UltraVNC MS-Logon II Weak Cryptography Vulnerability

UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNC_MsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DH_MAX_BITS controls the prime size). A 64-bit DH key can be broken by Pollard's rho algorithm in under one second on current hardware. Additionally, the private exponent is generated by the rng() function, which multiplies three libc rand() values seeded from time(NULL). With approximately 31 bits of internal state and a time-based seed, the private exponent is recoverable in under a minute by a passive observer. A network attacker who can observe the MS-Logon II handshake (via sniffing, recording, or man-in-the-middle) can derive the shared DH key and decrypt the encapsulated username and password, resulting in full credential disclosure. This affects legacy MS-Logon II connections; MS-Logon III (X25519 + AES-256-GCM) is unaffected.

ProductUltraVNC
CVSS7.4
EPSS0.0022
UpdatedJuly 15, 2026

Quick answer

UltraVNC should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 1.8.2.2

Fixed versions

  • No vendor fix published yet

How to fix it

UltraVNC is affected and no public fixed version is listed in the local advisory data yet. Reduce access, disable risky features where possible, and apply the vendor fix when it is released.

  1. Check where UltraVNC is installed and whether it is reachable from the internet.
  2. Limit access to trusted users, trusted networks, or a VPN until a vendor fix is available.
  3. Disable the affected feature or module if the advisory points to a specific upload, login, admin, chat, or network service path.
  4. Watch the vendor or advisory source and apply the first supported fix as soon as it is released.
  5. Review logs for strange access, failed attempts, crashes, file uploads, or unexpected account changes.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is no longer in the affected range.
  • Retest the affected page, API, upload, login, chat, container, or network flow.
  • Check logs after the change for blocked attempts, crashes, or errors.
  • Run a fresh Fixnx scan and save the report.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-7830?

UltraVNC versions listed as affected should be reviewed: <= 1.8.2.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.