Parallels DesktopApplication · Parallels

CVE-2021-27259

HIGH · 7.8 CVSS v3.1 Published 2021-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop 16.0.1-48919. An attacker must first obtain the ability to execute low-privileged code on the target guest system in order to exploit this vulnerability. The specific flaw exists within the Toolgate component. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before allocating a buffer. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the hypervisor. Was ZDI-CAN-12021.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow vulnerability in Parallels Desktop's Toolgate component allows a low-privileged attacker on a guest VM to escape into the hypervisor context by exploiting insufficient validation of user-supplied data during buffer allocation, leading to arbitrary code execution with hypervisor privileges.

MitigationApply Parallels Desktop security updates that address the Toolgate input validation flaw; ensure guest systems do not run untrusted code from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parallels DesktopApplication
Affected:= 16.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Parallels Desktop is installed
    Check for the presence of Parallels Desktop application on the host system. On macOS, look for /Applications/Parallels Desktop.app or check System Settings > Privacy & Security > Extensions for Parallels extensions.
    Affected if Parallels Desktop is not installed on the system.
  2. Identify installed Parallels Desktop version
    Open Parallels Desktop and navigate to Help > About Parallels Desktop, or run 'prlctl --version' command in Terminal if available, or check /Applications/Parallels Desktop.app/Contents/Info.plist for CFBundleVersion.
    Affected if The installed version is exactly 16.0.1.
  3. Verify Toolgate component status
    Check if Toolgate functionality is available by examining Parallels configuration files or running 'prlctl list -a' to list all VMs. Toolgate is a paravirtualization interface used for guest-to-host communication.
    Affected if Toolgate is enabled and VMs are running on the affected version 16.0.1.
  4. Determine if running as guest VM
    Identify whether this system is a guest VM by checking for Parallels-specific artifacts: look for prl_* kernel extensions, check system profiler for virtual hardware indicators, or run 'ioreg -l | grep -i parallels'.
    Affected if This system is a guest VM running on Parallels Desktop version 16.0.1 with Toolgate active.

The environment is affected if Parallels Desktop version 16.0.1 is installed and running, with the Toolgate component enabled and active guest VMs present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Parallels Desktop security updates that address the Toolgate input validation flaw; ensure guest systems do not run untrusted code from unknown sources.

Fix this in Parallels Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data