External risk intelligence

UpSnap Superuser Registration and RCE Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-49819

UpSnap is a web application designed for wake-on-lan management. Such tools are commonly deployed as web interfaces or management services that may be exposed to the network to facilitate remote device control, and the vulnerability exists in an API endpoint accessible to network-adjacent users.

OS Command Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the UpSnap wake-on-lan web application, potentially allowing unauthenticated attackers to gain full control of affected systems. This issue arises from a flaw in how the application handles initial superuser registration, which, if exploited, could lead to remote code execution. While this is a critical finding, the primary concern is confirming if this specific application is in use and if it's exposed in a way that attackers could reach it.

  • Unauthenticated access grants system control.
  • Important for potential remote system compromise.
  • Confirm usage and network exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can reach an API endpoint that initializes the superuser account on a vulnerable UpSnap instance. Because this endpoint lacks proper authentication and security checks, an attacker can register themselves as the initial superuser, obtain a long-lived authentication token, and subsequently gain root access to execute arbitrary commands on the server.

  • Network access is required.
  • Unauthenticated API call to initialize superuser.
  • Complete system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker on the same network to register a superuser account on UpSnap. This initial access could then be leveraged to execute arbitrary commands with root privileges on the underlying operating system, potentially leading to full system compromise.

  • System command execution.
  • Network-adjacent unauthenticated access.
  • Full system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in UpSnap affects network-adjacent attackers by allowing them to register an initial superuser account, obtain a long-lived JWT, and achieve root remote code execution. The first practical move is to identify all instances of UpSnap, determine their network exposure and business criticality, and then coordinate with the platform or application owner for remediation.

  • Platform or application owners should lead remediation.
  • Verify network exposure and criticality of UpSnap.
  • Plan coordinated updates during maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is UpSnap and how is it used?

UpSnap is a web-based application designed to manage Wake-on-LAN functionality, which allows users to remotely power on computers or servers across a network. It acts as a centralized management dashboard, often deployed as a service within a network environment to provide a convenient web interface for controlling the power states of connected hardware.

What does CVE-2026-49819 mean in plain English?

This vulnerability involves a missing authentication flaw that allows unauthorized users to perform actions meant only for administrators. Specifically, it combines a failure to verify identity with a lack of access control, categorized as weaknesses like improper privilege management and missing authentication. This allows an attacker to register a new superuser account and eventually run arbitrary commands on the system.

How does an attacker trigger this vulnerability?

An attacker triggers this by sending a specific request to the API endpoint responsible for initializing a new superuser account. The vulnerability only exists on fresh or uninitialized installations where no superuser account has been created yet. It is not triggered if a legitimate superuser has already been configured for the instance, as the system checks the account count before allowing registration.

Is my network at risk from CVE-2026-49819?

According to Halo Surface Signal, this vulnerability is particularly relevant if your UpSnap instance is accessible to network-adjacent users or exposed to the wider network. Because the weakness resides in an API endpoint that does not require login, any device or actor on the same network segment could potentially reach and exploit the service if it is not properly isolated.

What steps should I take if I run UpSnap?

Your first step is to inventory your environment to locate all running instances of UpSnap and confirm their version numbers. If you are using a version between 4.4.1 and 5.3.5, you should plan to update to version 5.4.0, which contains the fix. While preparing for the update, ensure the application is restricted from untrusted network access to minimize potential exposure.

References