Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-49819: Unauthenticated Initial Superuser Registration Leading to Root RCE in UpSnap

Published Aug 12, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS1.1%66th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-49819CWE-306 · Missing Authentication for…

CVE-2026-49819 is a critical vulnerability chain in UpSnap, a wake-on-LAN web application, affecting versions 4.4.1 through 5.3.5. The flaw originates in the initial superuser setup handler, pb.HandlerInitSuperuser, which is exposed through the init-superuser API endpoint. This functionality lacks authentication and other protective controls, including a setup token check, IP allow-listing, and rate limiting. Access is gated only by a totalSuperusers > 0 count check, which is false on a fresh installation. As a result, an unauthenticated attacker with network access to a newly deployed instance can create the first superuser account and obtain a long-lived JWT. With superuser access, the attacker can then reach a command-execution path in the wake functionality, where shell commands are invoked through /bin/sh -c, resulting in root-level remote code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to take over a fresh UpSnap deployment by registering the initial superuser account. The attacker can obtain persistent privileged application access via a long-lived JWT, fully compromise administrative control of the application, and then escalate to root-level remote code execution through the wake command execution path. This can result in complete loss of confidentiality, integrity, and availability of the affected host and the application it serves.

Mitigation

If you can’t patch tonight, do this now.

Until the fixed version can be deployed, restrict network access to the application so that untrusted users cannot reach the initial setup interface, especially on newly installed instances. Avoid exposing fresh deployments to untrusted networks before legitimate initialization is completed. Place the service behind trusted administrative network boundaries or equivalent access controls and monitor for unexpected superuser creation or other signs of unauthorized initialization activity.

Remediation

Patch, then assume compromise.

Upgrade UpSnap to version 5.4.0 or later, which fixes the vulnerable initialization flow. Review deployed instances for unauthorized superuser accounts created during initial setup exposure and remove any that were not legitimately provisioned. In environments where compromise is suspected, invalidate issued JWTs, rotate relevant credentials and secrets, and perform host-level incident response because exploitation may have resulted in root command execution.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-49819 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49819 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49819?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-49819.
Is there a patch for CVE-2026-49819?
Upgrade UpSnap to version 5.4.0 or later, which fixes the vulnerable initialization flow. Review deployed instances for unauthorized superuser accounts created during initial setup exposure and remove any that were not legitimately provisioned.
How severe is CVE-2026-49819?
CVE-2026-49819 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.1% (66th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.