Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 13 Aug 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 13 Aug 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Seriousm4x
Seriousm4x upsnap |
|
| Vendors & Products |
Seriousm4x
Seriousm4x upsnap |
Wed, 12 Aug 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | UpSnap - Unauthenticated Initial-Superuser Takeover Chains to Root RCE via wake_cmd | |
| Weaknesses | CWE-269 CWE-306 CWE-78 CWE-862 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-13T13:08:59.003Z
Reserved: 2026-06-01T18:50:36.055Z
Link: CVE-2026-49819
Updated: 2026-08-13T13:08:56.516Z
Status : Received
Published: 2026-08-13T00:17:32.747
Modified: 2026-08-13T13:19:09.937
Link: CVE-2026-49819
No data.
OpenCVE Enrichment
Updated: 2026-08-13T09:47:32Z