dbcve.org
SynapseApplication · Razer

CVE-2025-9869

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 Macro Module 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 Synapse Service. By creating a symbolic link, an attacker can abuse the service 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-26374.

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 Razer Synapse Service contains a link following vulnerability where it follows symbolic links created by attackers. By placing a symlink in a location the service accesses, an attacker can cause the service to delete arbitrary files. Chaining this file deletion with critical system file removal (like security DLLs or ETW providers) allows privilege escalation from low-privileged user to SYSTEM context.

MitigationApply vendor patch from Razer when available. Until then, disable or restrict the Razer Synapse Service if feasible, and limit file system permissions on directories accessed by the service.

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 installation
    Open Windows Services (services.msc) and look for 'Razer Synapse Service' or check Programs and Features for Razer Synapse entry
    Affected if The service or program entry exists on the system
  2. Check installed Razer Synapse version
    Open Add or Remove Programs, find Razer Synapse, and note the version number displayed; or check the version in the service properties
    Affected if The version number is lower than 3.10.730.71519
  3. Verify Razer Synapse service status
    Open Services, locate 'Razer Synapse Service', and check if its Status shows 'Running'
    Affected if The service is currently running
  4. Assess symlink placement risk
    Identify directories accessible to your user account that the Razer Synapse Service reads from or writes to; check if low-privileged users can create files or symlinks in those directories
    Affected if Low-privileged users can create symbolic links in directories accessed by the service, allowing file deletion escalation

You are affected if Razer Synapse version is below 3.10.730.71519, the service is running, and low-privileged users can create symlinks in directories the service accesses.

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 patch from Razer when available. Until then, disable or restrict the Razer Synapse Service if feasible, and limit file system permissions on directories accessed by the service.

Recommended fix Moderate confidence

Razer Synapse 3 version 3.10.730.71519 or later

  1. 1. Verify the current installed version of Razer Synapse 3 by opening the application and checking Help > About, or checking Add/Remove Programs
  2. 2. Navigate to the official Razer website and download the latest version of Razer Synapse 3
  3. 3. Uninstall the current version of Razer Synapse 3 through Windows Settings > Apps > Razer Synapse 3
  4. 4. Install the downloaded latest version of Razer Synapse 3
  5. 5. Restart the computer to ensure the service runs with the updated version
  6. 6. Verify the installed version is 3.10.730.71519 or later
Caveat Standard software upgrade considerations apply - verify compatibility with other Razer software and macro configurations before production deployment

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

Fix this in Synapse Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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