News Date: 2026-09-16
A local privilege-escalation vulnerability in Parallels Desktop for Mac creates an uncomfortable security gap for organizations that use Macs to operate Windows and Linux virtual machines. The flaw, named ParaShells and tracked as CVE-2026-90894, can allow software running under a standard macOS account to execute code with root privileges.
How the Privilege Escalation Works
Parallels installs a background component called prl_disp_service, which runs as root because it performs privileged operations such as configuring host networking and unpacking virtual machine appliances. According to the research, the service exposes a socket that can be accessed by ordinary local processes without requiring a trusted Parallels code signature.
The vulnerable appliance installation process builds a command for the macOS tar utility using a destination folder partly controlled by the requesting user. A specially constructed folder name can interfere with how that command is divided into arguments. An attacker can consequently introduce an additional tar option that launches another program. Because the archive operation is performed by the privileged Parallels service, the injected program also runs as root.
The attack is not remotely exploitable by itself. An intruder must already be able to execute code as a normal user. That limitation should not make enterprises dismiss the risk. A malicious package installation script, poisoned development dependency, compromised build process or abused shared account could provide the required starting point.
The Intel Mac Problem
JFrog says the corrective change is present in Parallels Desktop 27, with organizations advised to install the newest available release in that product line. However, version 27 requires Apple silicon and cannot be installed on Intel-based Macs. The latest Parallels Desktop 26 release available to Intel users is not described by the researchers as containing the relevant correction.
Recommended Defensive Actions
- Inventory every Mac running Parallels Desktop and record its hardware architecture.
- Upgrade compatible Apple silicon systems to the latest version 27 build.
- Restrict local accounts and interactive access on vulnerable Intel Macs.
- Monitor launch agents, launch daemons and sudo configuration for persistence.
- Use endpoint controls to limit unapproved package managers and development scripts.
I believe the larger lesson concerns product lifecycle dependencies. A security fix that requires new hardware is not a complete enterprise remediation strategy. Organizations retaining Intel Macs should demand clear vendor guidance while reducing local execution opportunities and planning accelerated replacement where exposure cannot be adequately contained.