dbcve.org
SynapseApplication · Razer

CVE-2025-9871

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 Chroma Connect 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 Razer Chroma SDK 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-26373.

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

This is a local privilege escalation vulnerability in the Razer Synapse 3 Chroma SDK installer. The flaw allows attackers to create a symbolic link that the installer follows to delete arbitrary files on the system, enabling elevation to SYSTEM privileges and execution of arbitrary code.

MitigationApply the vendor patch or update Razer Synapse 3 to the latest version. Until patched, avoid running the Razer Chroma SDK installer with elevated privileges.

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. Verify Razer Synapse 3 is installed
    Check for the presence of the Razer Synapse 3 installation directory, typically at C:\Program Files\Razer\Synapse3 or C:\Users\%username%\AppData\Local\Programs\synapse3
    Affected if The directory does not exist and the product is not installed, then the vulnerability does not apply
  2. Locate the installed version number
    Open the Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Razer\Synapse3\Config, or check the version property of the file C:\Program Files\Razer\Synapse3\Razer Synapse 3.exe by right-clicking and selecting Properties
    Affected if The version shown is less than 3.10.730.71519
  3. Check for recent Chroma SDK installer activity
    Look for installer log files in %TEMP% with names containing 'Chroma' or 'SDK', or check Add/Remove Programs for Razer Chroma SDK installation entries
    Affected if The Chroma SDK installer was recently run on the system
  4. Verify symbolic link vulnerability conditions
    Inspect the %TEMP% folder for any newly created symbolic links or junction points during/after installer execution, and check if the installer was run with elevated privileges
    Affected if The installer runs with administrator or SYSTEM privileges and can be made to follow a crafted symbolic link

The system is affected if Razer Synapse 3 is installed with a version lower than 3.10.730.71519 and the Chroma SDK installer has been or can be run with elevated privileges.

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 the vendor patch or update Razer Synapse 3 to the latest version. Until patched, avoid running the Razer Chroma SDK installer with elevated privileges.

Recommended fix Moderate confidence

Razer Synapse 3 version 3.10.730.71519 or later

  1. 1. Check the current version of Razer Synapse 3 installed on the system by opening the application and navigating to Settings > About, or by checking Add/Remove Programs
  2. 2. If the installed version is earlier than 3.10.730.71519, download the latest version of Razer Synapse 3 from the official Razer website (https://www.razer.com/synapse)
  3. 3. Uninstall the current version of Razer Synapse 3 through Windows Settings > Apps > Razer Synapse 3
  4. 4. Restart the computer to ensure all services are stopped
  5. 5. Install the newly downloaded Razer Synapse 3 version (3.10.730.71519 or later)
  6. 6. After installation, verify the installed version matches or exceeds 3.10.730.71519
  7. 7. Restart the computer to ensure the updated service runs correctly
Caveat Standard upgrade - no known breaking changes for end users; ensure peripheral configurations are backed up if applicable

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

Fix this in Synapse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9871 — 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-9871 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