Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local user session
-
DeliveryConnect to RzUpdateService named pipe endpoint
-
ExploitSend crafted lpThreadParameter payload via pipe
-
ExecutionService processes argument without privilege enforcement
-
PersistArbitrary code executes in SYSTEM context
-
ImpactFull local system compromise achieved
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a local interactive or remote desktop session on a Windows system running Razer RzUpdateService 1.10.14.0, with the attacker holding at minimum a low-privileged local or domain user account (CVSS 4.0 PR:L - unauthenticated or guest-level access is insufficient). No special system configuration is required beyond a default Razer software installation with RzUpdateService in a running state. The named pipe must be accessible to the standard user account, which is typical in default Razer deployments. Limiting factors include: (1) exploitation is strictly local - no remote network vector (AV:L); (2) a valid user session is required (PR:L); (3) RzUpdateService must be installed and actively running; (4) no impact extends beyond the local machine (SC:N/SI:N/SA:N per CVSS 4.0). This vulnerability does not directly enable remote exploitation or lateral movement, but it is a reliable escalation step in a multi-stage attack chain following initial access. |
| Impact | The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) with a score of 7.1 characterizes this as a low-complexity local escalation requiring only a standard user account - no attack prerequisites and no user interaction. Vulnerable-system impact is full across confidentiality, integrity, and availability (VC:H/VI:H/VA:H), while subsequent-system impact is absent (SC:N/SI:N/SA:N), confirming exploitation is confined to the local host. The CVSS 4.0 threat metric E:P confirms a proof-of-concept is present in the scoring, consistent with the public writeup at opcodic.notion.site. No EPSS data was provided in the input, so exploitation probability cannot be quantified. The vulnerability is not in CISA KEV, suggesting no confirmed mass exploitation at time of analysis. The primary real-world risk profile is as a post-initial-access privilege escalation primitive: an attacker who has obtained any local user account on a Windows machine with Razer software can reliably escalate to SYSTEM. In enterprise or gaming-lab environments with shared workstations and Razer peripherals, this is a meaningful lateral-movement enabler. No vendor patch has been identified, which materially increases urgency. The CPE wildcard version specifier in the NVD entry suggests versions beyond 1.10.14.0 may also be affected and should be verified with Razer. |
| Exploit ScenarioDerived | A standard domain user on a shared Windows workstation equipped with Razer peripherals connects to the RzUpdateService named pipe using the publicly available proof-of-concept and submits a crafted lpThreadParameter payload. The service, running as SYSTEM, processes the argument without enforcing privilege boundaries, resulting in arbitrary code execution in the SYSTEM context. The attacker now holds full local administrative control, enabling credential dumping, persistence installation, or lateral movement via harvested credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Aug 03, 2026
Privilege escalation in Razer RzUpdateService 1.10.14.0 allows a local low-privileged user to gain SYSTEM-level access by manipulating the lpThreadParameter argument processed by the service's Named Pipe Handler. The service, which runs at elevated Windows privilege, fails to enforce proper privilege boundaries when handling named pipe input (CWE-269), enabling a local user to leverage the service's execution context against the underlying system. A public proof-of-concept is confirmed available; the vulnerability is not currently listed in CISA KEV, though the low attack complexity combined with the published POC elevates real-world risk in environments with Razer hardware deployed.
Earlier versions of this analysis (1)
Privilege escalation in Razer RzUpdateService 1.10.14.0 allows a local low-privileged Windows user to gain elevated system privileges by manipulating the lpThreadParameter argument through the service's Named Pipe Handler in RzUpdateService.exe. The root cause is CWE-269 (Improper Privilege Management), where the update engine service fails to adequately restrict or validate what callers can trigger via its IPC named pipe interface. A public exploit exists, and the CVSS 4.0 score of 8.5 reflects full confidentiality, integrity, and availability impact on the affected host; no CISA KEV listing has been identified at time of analysis.
RemediationAI
No vendor-released patch has been identified at time of analysis - remediation version not independently confirmed. Until Razer issues an official fix, the most effective compensating control is to stop and disable the RzUpdateService Windows service, which eliminates the named pipe attack surface entirely: run 'sc stop RzUpdateService && sc config RzUpdateService start=disabled' from an elevated prompt. The trade-off is that automatic Razer software and driver updates will no longer function. As an alternative, restrict named pipe access using Windows security descriptor policies to limit which accounts can connect to the service's pipe endpoint, preventing low-privileged users from interacting with it while preserving service functionality - this requires identifying the pipe name via tools such as Process Monitor or Pipelist. In high-security environments where Razer peripherals are not required, consider uninstalling Razer software entirely. Monitor for patch availability via https://vuldb.com/vuln/385529 and the exploit writeup at https://opcodic.notion.site/Privilege-Escalation-via-Insecure-Named-Pipe-in-RzUpdateService-2d88e7fec518803fa5decf10fb0e1e27.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
RzUpdateService (CPE: cpe:2.3:a:razer:rzupdateservice:*:*:*:*:*:*:*:*) is Razer's hardware driver update engine, installed as a privileged Windows service on systems running Razer peripheral software, with the binary at C:\Program Files (x86)\Razer\RzUpdateEngineService\RzUpdateService.exe. The vulnerability exists in the service's Named Pipe Handler - Named Pipes are a Windows IPC mechanism that allow processes to exchange data with a service; when the service runs as SYSTEM and exposes a pipe accessible to lower-privileged users, it becomes an attractive local escalation target. The lpThreadParameter argument is a pointer value typically supplied to Windows thread creation APIs (e.g., CreateThread), and its mishandling indicates the service passes or acts on attacker-controlled data within a privileged execution context without adequate validation. CWE-269 (Improper Privilege Management) identifies the root cause as a failure to restrict the privilege level under which operations triggered by this argument execute, rather than a classic memory corruption flaw.
Know when Rzupdateservice 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
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Local-only vector (AV:L), low-privilege account required (PR:L), no user interaction needed; scope unchanged (S:U) consistent with CVSS 4.0 SC:N - impact confined to local machine.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A weakness has been identified in Razer RzUpdateService 1.10.14.0. Affected by this vulnerability is an unknown functionality of the file C:\Program Files (x86)\Razer\RzUpdateEngineService\RzUpdateService.exe of the component Named Pipe Handler. Executing a manipulation of the argument lpThreadParameter can lead to improper privilege management. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure.
Executive ViewAI
Razer RzUpdateService 1.10.14.0 contains a local privilege escalation vulnerability enabling low-privileged users to gain SYSTEM-level access through Named Pipe manipulation. Organizations with Razer peripherals deployed face complete system compromise risk; a public proof-of-concept exists with no vendor patch currently available. Immediate mitigation is required to protect enterprise endpoints.
Restrict file system and registry write access to the RzUpdateService Named Pipe Handler for non-administrator accounts; disable or uninstall the service on non-critical systems; implement application whitelisting to prevent exploitation chain execution; audit and remediate unnecessary local user privilege elevation paths; monitor vendor security advisories for patch availability.
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.
EUVD-2026-52351
GHSA-75gv-422j-4v8h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB