Skip to main content
Mallory
CriticalVulnerability

CVE-2026-49481: UpSnap Device Management OS Command Injection

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.6Critical · v3.1
EPSS1.5%74th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-49481CWE-78 · Improper Neutralization of Special…

CVE-2026-49481 is an authenticated OS command injection vulnerability in seriousm4x UpSnap versions earlier than 5.4.0. Device-management functionality unsafely interpolates user-controlled IP and MAC address fields into the wake and shutdown command templates. The resulting commands are executed by the host operating system's shell without input sanitization, enabling a permitted low-privileged user to inject arbitrary commands.

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 provides authenticated remote code execution on the server hosting UpSnap. An attacker can execute arbitrary operating-system commands with the privileges of the UpSnap service, potentially compromising confidentiality and integrity of accessible resources. The reported CVSS v3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N.

Mitigation

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

Until the upgrade can be applied, restrict device creation and editing privileges to fully trusted administrators, as exploitation requires the ability to supply or modify device IP or MAC field values.

Remediation

Patch, then assume compromise.

Upgrade UpSnap to version 5.4.0 or later, which patches CVE-2026-49481.

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-49481 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49481 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49481?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49481.
Is there a patch for CVE-2026-49481?
Upgrade UpSnap to version 5.4.0 or later, which patches CVE-2026-49481.
How severe is CVE-2026-49481?
CVE-2026-49481 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 1.5% (74th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

9 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 activity8Community discussion across Reddit, Mastodon, and other social sources.