dbcve.org
SynapseApplication · Razer

CVE-2025-9870

HIGH · 7.8 CVSS v3.0 Published 2025-10-29
Fix available
A fix is available. Upgrade to 3.10.730.71519 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
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.

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 confidence

The vulnerability exists in the Philips HUE module installer of Razer Synapse 3. Attackers with low-privileged code execution can create a symbolic link to trick the installer into deleting arbitrary files, achieving privilege escalation to SYSTEM context and arbitrary code execution.

MitigationApply vendor patches from Razer for Synapse 3 when available; until then, consider uninstalling the Philips HUE module or restricting user permissions to prevent symlink creation in installer directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SynapseApplication
Affected:< 3.10.730.71519

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Razer Synapse 3 is installed
    Look for Razer Synapse 3 in the list of installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\Razer\Synapse3)
    Affected if Razer Synapse 3 is not found on the system, the vulnerability does not apply
  2. Identify installed version of Razer Synapse 3
    Open Razer Synapse 3 and navigate to Settings > About, or right-click the Synapse tray icon and select 'Check for Updates' to reveal the current version number
    Affected if The installed version is lower than 3.10.730.71519 (any version before this threshold is affected)
  3. Check if Philips HUE module is present
    In Razer Synapse 3, go to the Modules or Devices section and look for the Philips HUE integration, or check for a HUE-related DLL or module folder within the Synapse3 installation directory
    Affected if The Philips HUE module is not installed or present, the specific attack surface may not be reachable
  4. Inspect installer directory permissions
    Locate the Razer Synapse 3 installation folder (typically in Program Files) and check write permissions on subdirectories related to module installation, particularly any folder containing 'HUE' or 'installer' in the name
    Affected if Low-privileged users can create symbolic links or new files in the module installer directories, making the symlink attack feasible

You are affected if Razer Synapse 3 version is below 3.10.730.71519 AND the Philips HUE module is installed AND unprivileged users can create symlinks in the installer directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.10.730.71519 or later
Fixed in 3.10.730.71519
Interim mitigation

Apply vendor patches from Razer for Synapse 3 when available; until then, consider uninstalling the Philips HUE module or restricting user permissions to prevent symlink creation in installer directories.

Recommended fix Moderate confidence

Razer Synapse 3 version 3.10.730.71519 or later

  1. Open Razer Synapse 3 on the affected system
  2. Navigate to the settings or about section to check the current version number
  3. If an update is available, apply it through the built-in update mechanism
  4. Alternatively, download the latest version of Razer Synapse 3 from the official Razer website (https://www.razer.com/synapse)
  5. Run the installer and follow the prompts to complete the upgrade
  6. Verify the installed version is 3.10.730.71519 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Synapse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9870 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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