CVE-2026-49819: UpSnap - Unauthenticated Initial-Superuser Takeover Chains to Root RCE via wake_cmd
UpSnap is a wake on lan web app. Versions 4.4.1 through 5.3.5 are vulnerable to a missing-authentication / privilege-escalation chain in `pb.HandlerInitSuperuser` (`backend/pb/handlers.go:249`), reachable as `POST /api/upsnap/init-superuser`. The vulnerable code lacks any authentication, setup token, IP allow-list, or rate limit and is gated only by a `totalSuperusers > 0` count check — a condition that is false on every fresh install — allowing an unauthenticated network-adjacent attacker to register the initial superuser account, receive a long-lived JWT, and pivot to root remote code execution at `backend/networking/wake.go:43` (`exec.CommandContext(ctx, "/bin/sh", "-c", wake_cmd)`). Version 5.4.0 fixes the issue.
Security readout for executives and security teams
Plain-English summary
On a fresh, vulnerable UpSnap installation, an unauthenticated attacker who can reach the service may claim the first administrator account. That access can then be chained into commands running with root privileges, potentially allowing complete system takeover, data theft, disruption, or further network compromise.
Executive priority
Treat this as an immediate priority for reachable fresh installations and an urgent upgrade across all affected versions. Isolate unpatched systems and investigate any instance whose initial-superuser ownership cannot be verified.
Technical view
UpSnap 4.4.1 through 5.3.5 exposes initial-superuser creation without authentication or a setup token. The only gate checks whether a superuser already exists. An attacker claiming that account receives a long-lived JWT and can pivot to root command execution because wake_cmd is passed to /bin/sh -c. Version 5.4.0 fixes the issue.
Likely exposure
Highest exposure exists on fresh or uninitialized UpSnap 4.4.1–5.3.5 deployments reachable by untrusted clients. The described initialization path is blocked when the superuser count is already greater than zero, but all affected-version installations should still be inventoried and upgraded.
Exploitation context
The chain requires no prior privileges or user interaction and is rated CVSS 9.8. However, the source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation. Exploitation in the wild therefore remains unconfirmed.
Researcher notes
The chain combines missing authentication and authorization weaknesses with privilege escalation and shell command injection behavior, mapped to CWE-306, CWE-862, CWE-269, and CWE-78. The supplied sources do not provide exploitation telemetry, indicators of compromise, or detailed forensic artifacts.
Mitigation direction
Upgrade UpSnap to version 5.4.0 or later.
Until upgraded, prevent untrusted access to UpSnap, especially on fresh or uninitialized deployments.
Verify initial-superuser ownership; treat any unknown administrator as a potential compromise.
Review the vendor advisory and 5.4.0 release information before restoring normal exposure.
Validation and detection
Inventory UpSnap instances and flag versions 4.4.1 through 5.3.5.
Confirm each affected instance has an authorized initial superuser.
Verify the deployed UpSnap version reports 5.4.0 or later.
Confirm unauthenticated clients cannot initialize a superuser after remediation.
Review available account and access records for unexpected superuser creation or token use.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.