CVE-2021-34868
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 · uneditedThis vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop 16.1.3-49160. 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 uncontrolled memory allocation. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the hypervisor. Was ZDI-CAN-13712.
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 confidenceThis is a local privilege escalation vulnerability in Parallels Desktop's Toolgate component. The flaw stems from improper validation of user-supplied data leading to uncontrolled memory allocation, which an attacker with low-privileged code execution on the guest VM can exploit to escalate privileges and execute arbitrary code in the hypervisor context.
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= 16.1.3-49160CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Parallels Desktop versionCheck the Parallels Desktop version information through the application UI (Parallels Desktop menu > About Parallels Desktop) or by running the version check command for your Parallels installationAffected if The installed version matches exactly 16.1.3 build 49160
-
Confirm Toolgate component is activeVerify that the Toolgate component is loaded and operational in the current Parallels Desktop installation - this is typically a core component used for guest-to-host communicationAffected if Toolgate is present and enabled in the Parallels Desktop environment
-
Check for guest VM tool integrationsInspect whether Parallels Tools are installed and running within guest virtual machines, as the Toolgate vulnerability is exploited from within the guest VM contextAffected if Parallels Tools are installed in any guest VM on this host
You are affected if your Parallels Desktop installation is exactly version 16.1.3 build 49160 and the Toolgate component is enabled, as this specific build contains the vulnerability in the Toolgate component that allows guest-to-host privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the vendor-supplied patch/update for Parallels Desktop. Until patched, restrict VM access to trusted users and minimize the attack surface of guest systems.
Parallels Desktop 17.x or later (current stable release recommended)
- 1. Verify the current Parallels Desktop version by navigating to Parallels Desktop > About Parallels Desktop
- 2. If version 16.1.3-49160 or any version below 17.0 is installed, download and install the latest version of Parallels Desktop from the official Parallels website (www.parallels.com/products/desktop/download/)
- 3. Alternatively, check for updates via Parallels Desktop > Check for Updates
- 4. After upgrading, verify the new version number to confirm the update was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34868 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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