Razer Synapse 3 CVE-2025-9870
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local code execution
-
DeliveryPlant symbolic link targeting installer path
-
ExploitTrigger Philips HUE module uninstall/installer
-
ExecutionPrivileged process follows link, deletes arbitrary file
-
ImpactEscalate to arbitrary code execution as SYSTEM
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires the attacker to already have the ability to execute low-privileged code on the target (local foothold). The specific trigger is the Razer Synapse 3 Philips HUE module installer/uninstaller performing a file operation that follows an attacker-created symbolic link, enabling arbitrary file deletion as a privileged process. Affected product is Razer Synapse 3 on Windows, which generally implies installed Razer peripheral software. Limiting factors: no remote vector (local access mandatory), the privileged installer/uninstall routine must be invoked, and the attacker needs filesystem write access to plant the symlink in the targeted location. |
| Impact | This is a credible but second-tier priority. The CVSS 3.0 vector (AV:L/AC:L/PR:L/UI:N, base 7.8 HIGH) correctly characterizes a local privilege escalation: an attacker must already run low-privileged code on the host, so there is no remote or network exposure despite the full C:H/I:H/A:H impact (abuse of an arbitrary-file-delete primitive to reach SYSTEM). The exploitation signals are weak-to-moderate: EPSS is only 0.19% (8th percentile), this CVE is NOT in CISA KEV, and no public exploit code is referenced - only the ZDI advisory. These signals are consistent with each other (low probability + no confirmed exploitation + no POC) rather than conflicting, so there is no evidence of active or widespread abuse. The 'RCE' tag overstates reach: the CVSS vector is AV:L and the description explicitly scopes this to local attackers, so it is local-only code execution as SYSTEM, not remote code execution - treat it as an LPE for patch-prioritization. Net: a real local EoP worth patching on a normal cycle, not an emergency, as it requires a foothold the attacker must already have obtained. |
| Exploit ScenarioDerived | A low-privileged user (or malware already running as a standard user) plants a symbolic link that redirects a file operation performed by the Razer Synapse 3 Philips HUE module installer/uninstaller. When the privileged installer process follows the link, it deletes an attacker-chosen file, which is leveraged to gain code execution as SYSTEM. No public exploit code is referenced, and exploitation requires prior local access with the ability to run low-privileged code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Local privilege escalation in Razer Synapse 3 allows an attacker who already holds a low-privileged foothold on a Windows host to abuse the Philips HUE module uninstaller's link-following file operation and delete arbitrary files as SYSTEM, then leverage that to execute code with SYSTEM privileges. Affected installations are those running the Razer Synapse 3 software with the Philips HUE module present; the flaw is a classic symbolic-link (CWE-59) issue in a privileged installer/uninstaller routine. There is no remote vector - the attacker must already be able to run code and write to the targeted filesystem location - and no public exploit code was identified at time of analysis, with EPSS at 0.19% (8th percentile).
RemediationAI
No vendor-released patch identified at time of analysis, and the provided references point only to the ZDI advisory (https://www.zerodayinitiative.com/advisories/ZDI-25-921/), which should be checked for a vendor-supplied fix version before applying any version-specific guidance. Until a patched Synapse 3 build is confirmed, apply compensating controls that break the symlink-following precondition: ensure the installation directory for Synapse 3 and the Philips HUE module (typically under Program Files and ProgramData) is writable only by Administrators and SYSTEM, since the attack requires the low-privileged user to plant a reparse point in a path the installer touches - tightening these ACLs has the trade-off of requiring elevation for legitimate module updates. If the Philips HUE integration is not in use, remove or disable the HUE module so the vulnerable uninstaller path is never present, accepting the loss of Hue lighting sync; organizations that must retain it can restrict interactive logon and local code execution on machines running Synapse 3, reducing the local foothold the exploit depends on. Additional detection-oriented measures include auditing and alerting on symbolic link, junction, or mount-point creation in Synapse install and temp directories, and monitoring process creation where the Synapse uninstaller spawns unexpected child processes. Note that these are mitigations, not fixes; the durable remedy is the vendor patch once released.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-59, Improper Link Resolution Before File Access ('Link Following'), in the Razer Philips HUE module uninstaller shipped with Razer Synapse 3. Privileged Windows installer and uninstaller components frequently perform cleanup operations - deleting files or directories in predictable paths - under SYSTEM or elevated context. If the process follows a reparse point (symbolic link, junction, or hardlink) created by a lower-privileged user instead of validating the resolved target, the deletion is redirected to an arbitrary file. Because the deleting process runs with high integrity, it can remove files that the attacker could never touch directly, which in Windows commonly enables tampering with service binaries, scheduled-task executables, or protected configuration, yielding SYSTEM-level code execution. The CPE data (cpe:2.3:a:razer:synapse:*:*:*:*:*:*:*:*) indicates the CPE does not version-scope the product, so any Synapse 3 installation carrying the vulnerable HUE module should be treated as potentially affected until the vendor confirms fixed builds. The issue was reported through Trend Micro's Zero Day Initiative as ZDI-CAN-26375 and published as ZDI-25-921.
Know when Synapse gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local foothold required (AV:L) with low privileges (PR:L) and no user interaction; symlink-to-SYSTEM file-delete primitive yields full C/I/A impact on the host.
Primary rating from Vendor (trendmicro).
CVSS VectorVendor: trendmicro
DescriptionCVE.org
Razer Synapse 3 RazerPhilipsHueUninstall Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Razer Synapse 3. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
The specific flaw exists within the Philips HUE module installer. By creating a symbolic link, an attacker can abuse the installer to delete arbitrary files. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-26375.
Executive ViewAI
Razer Synapse 3 installations with the Philips HUE module on Windows endpoints are affected by a high-severity local privilege escalation flaw that could allow an attacker with an existing low-privileged foothold to gain SYSTEM-level control. This matters to leadership because successful exploitation could enable deeper endpoint compromise, data access, and persistence on affected systems, though it is not remotely exploitable and no public exploit code was identified at the time of analysis.
Remove or disable the Razer Synapse 3 Philips HUE module on non-essential endpoints; enforce least privilege and remove unnecessary local administrator rights; restrict low-privileged write access to application install and temporary paths; monitor EDR for uninstaller processes following symbolic links or writing to privileged locations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse 2.20.15.1104 that is forwarded to ZwOpe
In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). Rated critical seve
Matrix Synapse before 1.5.0 mishandles signature checking on some federation APIs. Rated critical severity (CVSS 9.8), t
Multiple system services installed alongside the Razer Synapse 3 software suite perform privileged operations on entries
Multiple system services installed alongside the Razer Synapse 3 software suite perform privileged operations on entries
Matrix Synapse before 0.33.3.1 allows remote attackers to spoof events and possibly have unspecified other impacts by le
Synapse is an open source Matrix homeserver implementation. Rated high severity (CVSS 7.1), this vulnerability is remote
Razer Synapse 2.20.15.1104 and earlier uses weak permissions for the CrashReporter directory, which allows local users t
Synapse is an open-source Matrix homeserver written and maintained by the Matrix.org Foundation. Rated medium severity (
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Rated high severity (CVSS 8.2)
Local privilege escalation in Razer Synapse 3 lets an attacker who already holds a low-privileged foothold on a Windows
Local privilege escalation in Razer Synapse 3 lets an attacker who already has low-privileged code execution on a Window
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB