Safeguard
Vulnerability Analysis•

CVE-2023-3181: High Privilege Escalation in Splashtop for Windows

CVE-2023-3181 is a high severity local privilege escalation in Splashtop software on Windows. Mandiant lists version 1.5.6.23 as the fix, so update.

Safeguard Security Team
3 min read

CVE-2023-3181 is a high severity (CVSS 7.8) local privilege escalation in Splashtop software on Windows. A standard user can abuse a temporary updater file that runs as SYSTEM. Mandiant reports the issue was fixed in version 1.5.6.23, so update affected Splashtop installs to that version or later.

What's affected

The NVD record describes the Splashtop Software Updater uninstaller, which creates a folder under the Windows temp directory and copies itself there as a file named Au_.exe. That file is launched as SYSTEM after a reboot, or when a standard user runs an MSI repair through the Splashtop Streamer Windows installer.

The record lists Splashtop products (Splashtop Business, Mirroring360 Sender and Mirroring360 Receiver) and Microsoft Windows as affected configurations. It does not give a version range. The Mandiant disclosure says the issue was fixed in version 1.5.6.23 and does not name the product line that number belongs to, so confirm the matching fixed build for each Splashtop product you run with the vendor.

The weakness needs local access with a standard account. It is not a remote attack on its own, which is why the score sits in the high range rather than critical.

How to check if you're exposed

On a Windows machine you can read the installed Splashtop version from the registry uninstall keys. Run this in PowerShell and compare the version column with 1.5.6.23.

Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object DisplayName -like "*Splashtop*" | Select-Object DisplayName, DisplayVersion

Use your endpoint management tool to run the same query across the fleet. Pay extra attention to shared machines, kiosks and terminal servers, because the risk is a lower privileged user gaining SYSTEM on a host they can already log in to.

What to do now

  1. Inventory every Windows host with a Splashtop component, including the Streamer and Mirroring360 tools.
  2. Update to the fixed release from Splashtop. Mandiant names 1.5.6.23, but check the vendor download page for the build that matches your product.
  3. Where you cannot update yet, limit who has interactive logins on the affected hosts.
  4. Review permissions on the Windows temp directory and watch for unexpected executables launched by the updater after reboot.
  5. Add Splashtop to your regular third party software review so the next updater issue is caught by version, not by chance.

Why it matters

The CWE for this record is CWE-379, which covers files and directories created in a location that other users can reach. Here the updater trusts a folder that inherits permissions from the shared temp directory, and the copied program loads libraries from its own folder. A standard user who can write there can influence what a SYSTEM process loads.

This class of bug is common in installers and updaters because they run with high privilege but are written as if the machine had one user. The fix is usually to create the working folder with locked down permissions. The record does not say the issue is exploited in the wild and it is not in the CISA KEV catalog.

Quick check

Is CVE-2023-3181 exploitable remotely?

The record describes a local issue. An attacker needs a standard user account on the Windows machine first, then uses the updater behavior to gain SYSTEM.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.