CVE-2026-27182
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSaturn Remote Mouse Server contains a command injection vulnerability that allows unauthenticated attackers to execute arbitrary commands by sending specially crafted UDP JSON frames to port 27000. Attackers on the local network can send malformed packets with unsanitized command data that the service forwards directly to OS execution functions, enabling remote code execution under the service account.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSaturn Remote Mouse Server has a command injection vulnerability in its UDP listener on port 27000. The service accepts JSON frames containing command data without sanitization and passes this data directly to OS execution functions, allowing unauthenticated attackers on the local network to execute arbitrary commands under the context of the service account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Saturn Remote Mouse Server is installedCheck for the application in installed programs (Windows: Programs and Features, Linux: package manager or check common install paths like /opt or /usr/local). Also check for running processes with name 'saturn' or 'remote-mouse'.Affected if The software is installed and running on the system
-
Confirm UDP listener on port 27000 is activeRun command 'netstat -anp | grep 27000' (Linux) or 'netstat -ano | findstr 27000' (Windows) to check if UDP port 27000 is listening. Also verify with 'netsh firewall show all' (Windows) or 'iptables -L' (Linux) for firewall rules on this port.Affected if UDP port 27000 is open and listening, indicating the vulnerable service is exposed on the network
-
Assess network exposure of the serviceReview firewall rules and network configuration to determine if port 27000 is accessible from untrusted network segments. Check if the service binds to 0.0.0.0 or an interface on a shared/public network rather than localhost only.Affected if The UDP service is bound to a network interface accessible from untrusted local network segments or the internet
-
Check service execution contextInspect the service configuration to determine under which user account the Saturn Remote Mouse service runs. On Windows: services.msc > find Saturn Remote Mouse service > right-click Properties > Log On tab. On Linux: check systemd service file or process owner.Affected if The service runs with elevated privileges (e.g., SYSTEM, root, or admin) which would amplify the impact of command injection
-
Compare installed version to any known releasesIf version information is accessible via the application (about dialog, --version flag, or registry on Windows), compare it to the latest available version from the vendor. Without specific version ranges, treat any exposed installation as potentially vulnerable.Affected if Unable to confirm the installed version includes fixes, or the version is outdated compared to any available patched release
A system is affected if Saturn Remote Mouse Server is installed with its UDP service on port 27000 exposed to untrusted network segments, regardless of the specific version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and sanitization on all UDP JSON frame data before passing to execution functions, or replace direct OS execution calls with safe API alternatives. Additionally, restrict network access to port 27000 via firewall rules to limit exposure to trusted local network segments.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data