CVE Tools

CVE-2026-90894

Parallels Desktop local privilege escalation via appliance extract argument injection

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether Parallels Desktop for Mac is installed and record its installed version.
  2. Identify Macs running a version earlier than 27.0.0.
  3. Upgrade Parallels Desktop for Mac to version 27.0.0 or later.
  4. Until upgraded, limit access to affected Macs to trusted local users and avoid appliance installation from untrusted folders.
  5. Review affected Macs for unexpected administrator-level changes or unfamiliar software installed by local accounts.

What it is

From the CVE record

Parallels Desktop runs prl_disp_service as root. Local clients reach it on the world-writable socket /var/run/prl_disp_service.socket. PrlSrv_LoginLocal accepts peer credentials. No Parallels signature. No admin group. After login, PrlSrv_InstallAppliance lets you pick the appliance folder (sVmParentPath). The daemon unpacks with one string, tar -xf "%1" -C "%2", then Qt QProcess::splitCommand chops that string into words. A quote in the folder name closes early. The leftover text becomes extra tar flags. macOS tar --use-compress-program= runs the named program as root.

In plain language

Written by AI from the record

Parallels Desktop for Mac before 27.0.0 lets a local standard user take full control of the Mac, so businesses using it should upgrade promptly.

Local authenticated privilege escalation in Parallels Desktop for Mac’s root service allows argument injection through a crafted appliance folder name during appliance installation, resulting in arbitrary command execution as root.

If you're affected

  • Full Mac takeover
  • Business data exposure
  • Security controls disabled
  • Operational disruption
  • Malware installation

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS5th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

0 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 5th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 4 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Parallels, not every advisory. This one: public exploit.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store