Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-7840 – Pre-Auth RCE via Global Buffer Overflow – UltraVNC Repeater ≤ 1.8.2.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-7840 is a critical global buffer overflow in the embedded HTTP administration server of the UltraVNC Repeater, affecting all versions through 1.8.2.2. An unauthenticated remote attacker can send a single crafted HTTP request to overflow a fixed internal buffer and achieve arbitrary code execution on the host running the repeater. The vulnerability carries a CVSS 3.1 score of 9.8 (Critical) and a CVSS 4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The functions wi_senderr() and wi_replyhdr() in repeater/webgui/webutils.c write attacker-supplied HTTP request URIs into a fixed 1000-byte global buffer (hdrbuf) via unchecked sprintf calls, with no bounds validation (CWE-787: Out-of-bounds Write).
  • Trigger conditions: The HTTP receive buffer (WI_RXBUFSIZE) accepts URIs up to approximately 150 KB. Sending a single HTTP request with a URI of 1,500 bytes or longer overflows hdrbuf by at least 500 bytes, corrupting adjacent .bss-segment globals.
  • Attack vector: Network-reachable, requires no privileges and no user interaction. The overflow is triggered before any authentication check executes. The repeater’s HTTP administration interface listens on TCP port 80 by default and is architecturally designed to be publicly accessible on a routable IP address.
  • Impact: Corruption of adjacent global memory in the .bss segment enables arbitrary remote code execution on the host running the repeater.

Affected software

  • UltraVNC Repeater all versions through 1.8.2.2

Severity

  • CVSS 3.1: 9.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS 4.0: 9.3 CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H

Mitigation and recommended actions

  • Immediate: Upgrade to UltraVNC 1.8.2.3 or later. Version 1.8.2.3 (June 2026) introduced dedicated repeater security fixes; the latest available release is 1.8.2.4.
  • If immediate patching is not feasible: Restrict network access to the repeater’s HTTP administration port (default TCP 80) using firewall rules or network-level access controls, blocking connections from any untrusted or unanticipated sources until patching can be completed.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge