# CVE-2026-49481: UpSnap vulnerable to Remote Code Execution via IP Field Template Injection in wake_cmd/shutdown_cmd

> Authenticated attackers can execute arbitrary OS commands on the server by injecting malicious input into device IP or MAC fields.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-6mc7-6948-w5h4

## What is CVE-2026-49481?

CVE-2026-49481 is a critical command injection vulnerability in seriousm4x UpSnap, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-49481?


## How do I fix CVE-2026-49481?

No fix has been published for CVE-2026-49481 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49481 being exploited?

There is no known exploitation of CVE-2026-49481 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49481 and fix it if it is affected.

What it is: CVE-2026-49481 is a critical command injection vulnerability in seriousm4x UpSnap, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49481 in the wild and no public exploit code.

Affected product: seriousm4x UpSnap. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49481/ (Markdown: https://insights.sbomify.com/CVE-2026-49481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49481
- OSV: https://osv.dev/vulnerability/CVE-2026-49481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49481/
Summaries are generated and may contain mistakes; the official description above is the record.