Parallels RAS Client: Local Vulnerability Allows Escalation to…

CVE-2026-18263 affects the RAS RDP Backend Service with a CVSS 7.8 score. An exposed dangerous function allows low-privilege code to elevate permissions to SYSTEM.

The Trend Micro Zero Day Initiative coordinated disclosure program publicly released advisory ZDI-26-556 on August 11, 2026, documenting a local privilege escalation vulnerability in the Parallels RAS remote access client. The flaw, identified as CVE-2026-18263, allows an attacker who already has low-privilege code execution on a system to elevate their rights to the SYSTEM context. The CVSS 3.0 score of 7.8 (HIGH severity) and vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicate low attack complexity and no user interaction required.

Key Takeaways

The RAS RDP Backend Service of the Parallels RAS Client exposes a dangerous function classified as CWE-749, enabling privilege escalation from low-privilege code to SYSTEM.
The attack vector is exclusively local (AV:L), with low complexity (AC:L) and no user interaction required (UI:N); impact is maximum on confidentiality, integrity, and availability (C:H/I:H/A:H).
The vulnerability was reported to the vendor on February 25, 2026; coordinated publication occurred after 168 days.
Available sources do not specify which Parallels RAS Client versions are affected nor details on the availability of a vendor patch.

How the Flaw Works

According to the ZDI advisory, the vulnerability resides in the RAS RDP Backend Service, a component of the Parallels RAS Client. The CWE-749 classification identifies the issue as an exposed dangerous method or function: the service exposes functionality that, when invoked, permits sensitive system operations without adequate access controls.

An attacker already positioned on the system with low-privilege code can exploit this function to achieve arbitrary code execution in the context of SYSTEM. The combination of PR:L (low privileges required) and UI:N (no user interaction) means that once an initial foothold is obtained, escalation is automatic.

"The specific flaw exists within the RAS RDP Backend Service. The issue results from an exposed dangerous function. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM." — ZDI Advisory ZDI-26-556

The Risk Profile: Why CVSS 7.8 with Local Attack Is Still Critical

The CVSS 7.8 score, while not reaching the 9.0+ threshold typical of remote vulnerabilities, masks high operational danger. The full vector CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H describes a flaw that, although requiring local access, is technically trivial to exploit once an initial foothold is gained. Per the official CVE record, severity is HIGH.

The pattern is particularly relevant for enterprise organizations deploying Parallels RAS Client across thousands of endpoints. In these environments, initial compromise often occurs via phishing or malicious software delivery. The presence of a local LPE with low complexity turns every single infection into potential full machine control.

The vector value AC:L (attack complexity low) is significant: no race conditions or specific target system configurations are required. The attacker does not need to bypass additional protection mechanisms or depend on particular software states. This predictability makes the vulnerability attractive to actors who already possess automated post-exploitation tooling.

The Disclosure Timeline: 168 Days Without Patch Indication

Coordinated disclosure data shows a significant timeframe: the vulnerability was reported to the vendor on February 25, 2026, but public advisory release occurred only on August 11, 2026. This 168-day interval is the data available in sources.

The patch URL indicated in the ZDI advisory points to the same advisory. According to available sources, the status of a vendor-released patch is not detailed. The absence of specific affected versions in primary sources introduces operational uncertainty for system administrators.

The researcher operated through the standard ZDI channel: private vendor notification, awaiting response, and coordinated publication at the embargo expiration. The internal ZDI identifier ZDI-CAN-28886 confirms case traceability in the program management system.

Immediate Actions

Verify Parallels RAS Client presence in enterprise endpoint software inventories, with particular attention to installed versions.
Contact Parallels directly or consult the vendor's official support portal to verify the release status of any corrective updates for CVE-2026-18263.
Review user account privileges on systems where the client is installed, limiting unauthorized code execution that constitutes the exploitation prerequisite where possible.
Monitor system logs for anomalous RAS RDP Backend Service activity, particularly child processes executed with elevated privileges unrelated to legitimate user operations.

The Disclosure Gap: When the Vendor Does Not Collaborate

The 168-day interval between reporting and coordinated publication, combined with the absence of a dedicated patch page in available sources, presents a case study on the limits of coordinated disclosure. The ZDI program provides for a private notification cycle, but the lack of documented corrective updates at publication time leaves enterprise users without clear operational guidance.

This scenario recurs in the client-side vulnerability landscape: primary sources converge on technical flaw details, but not on operational management. For administrators, the gap between disclosure and remediation is the real stake of the vulnerability, more than the CVSS score.

The ZDI advisory structure itself reflects this asymmetry: the technical section is exhaustive on the flaw mechanism, while the vendor section is reduced to a URL pointing back to the same document. This pattern, known to threat intelligence analysts, requires a proactive approach from software consumers.

Per available sources, information on CVE-2026-18263 is based on ZDI advisory ZDI-26-556 and the official CVE record. Affected versions, specific patches, and technical details of the exposed dangerous function are not documented in accessible sources.

Information has been verified against cited sources and is current as of publication.

Sources

Sources and references