Parallels RAS Client: LPE to SYSTEM After 168 Days of Waiting

ZDI-26-556 reveals an exposed dangerous function in the RAS RDP Backend Service. Local escalation to SYSTEM after 168 days of coordinated disclosure. Here are the gaps that remain.

Trend Micro's Zero Day Initiative has published advisory ZDI-26-556 covering a local privilege escalation vulnerability in the Parallels RAS desktop virtualization client. Coordinated disclosure occurred on August 11, 2026, roughly 168 days after the initial vendor report on February 25, 2026. The exposure window sits in a sector — remote desktop access and VDI — where backend services must run with elevated privileges by architectural necessity, amplifying the blast radius of any such flaw.

Key Takeaways

Vulnerability ZDI-26-556 resides in the Parallels RAS Client's RAS RDP Backend Service and exploits an exposed dangerous function for escalation to SYSTEM.
The attacker must already have the ability to execute low-privileged code on the target system: this is not a remotely exploitable flaw.
The associated CVE is CVE-2026-18263, currently in reserved status per the cve.org database.
Coordinated disclosure spans approximately 168 days between report and public advisory release.

The Mechanism: From Low-Privileged Code to SYSTEM

The specific flaw resides in the RAS RDP Backend Service, an infrastructure component of the Parallels RAS Client. According to the ZDI advisory, "the issue results from an exposed dangerous function": a potentially harmful function exposed without adequate access controls or input parameter validation.

An attacker who already has the ability to execute code with limited privileges on the system can trigger this function to elevate their rights to SYSTEM level and execute arbitrary code in that context. The impact is total compromise of the host Windows system, with full control over the device and its data.

"This vulnerability allows local attackers to escalate privileges on affected installations of Parallels RAS Client. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability."
— ZDI Advisory ZDI-26-556

The risk perimeter centers on multi-user environments: terminal servers, VDI infrastructures, and shared workstations where limited-privilege users operate daily on the same system. In these contexts, a single compromised account — or a malicious user with legitimate access — can become a vector for system takeover.

168 Days of Disclosure: A Delay That Weighs

The timeline published in the ZDI advisory records the vendor report on February 25, 2026 and coordinated release on August 11, 2026. The gap of roughly 168 days raises concrete questions about response speed in the desktop virtualization sector, where backend components require elevated privileges to function and every day of delay exposes significant risk.

No infrastructure overlaps link this specific vulnerability to known threat actors or documented campaigns: the current dossier includes no indicators of compromise or reports of in-the-wild exploitation. However, the local nature of the flaw — requiring prior system access — does not make it less relevant in enterprise contexts where initial compromise often occurs via other vectors (phishing, supply chain, stolen credentials).

The Black Holes in the Dossier: Versions, Patches, and CVSS

The ZDI advisory presents gaps that limit a complete operational reading of the threat. The CVSS score and vector are not stated in the published document, making objective severity quantification per the assessment standard impossible. Similarly, the specific Parallels RAS Client versions affected are not indicated in the dossier reviewed.

CVE-2026-18263, registered in the cve.org database, shows as reserved: no additional technical details are currently available through this channel. The lack of confirmation of a patch release from Parallels represents a further element of uncertainty: the URL listed in the advisory as the vendor patch URL points to the same ZDI advisory, without resolving to a specific vendor update.

What to Do Now

Verify the presence of Parallels RAS Client in your IT assets and map active installations, especially in multi-user environments with remote desktop access.
Consult Parallels official channels directly for updates on the availability of corrective patches for installed versions.
Review local access controls on systems hosting the client, limiting unauthorized code execution by limited-privilege users where possible.
Monitor the CVE-2026-18263 record for the potential publication of technical details and a CVSS score enabling more precise risk assessment.

The Service Privilege Problem

This case encapsulates a structural tension in virtualized environment security: backend services like the RAS RDP Backend must operate with elevated privileges to function, but any flaw in these components immediately becomes a direct path to SYSTEM. This is not a misconfiguration: it is an architectural choice that makes the attack surface particularly sensitive.

The combination of prolonged exposure — 168 days — with the absence of a CVSS score and clear information on affected versions leaves organizations in a state of operational uncertainty. Until Parallels clarifies patch status and details on affected versions, risk management remains an exercise in mapping and waiting, rather than active mitigation.

Frequently Asked Questions

Is the vulnerability remotely exploitable?

No. The ZDI advisory specifies that the attacker must already have the ability to execute low-privileged code on the target system. The flaw is a local privilege escalation, not remote code execution.

Which Parallels RAS Client version is vulnerable?

The dossier does not specify affected versions. The ZDI advisory generically indicates "affected installations of Parallels RAS Client" without versioning details.

Is an official patch available?

Not documented in the sources consulted. The URL indicated as the vendor patch URL in the ZDI advisory resolves to the same advisory, without pointing to a specific update released by Parallels.

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

Sources

Sources and references