CVE-2025-64740
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 · uneditedImproper verification of cryptographic signature in the installer for Zoom Workplace VDI Client for Windows may allow an authenticated user to conduct an escalation of privilege via local access.
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 · moderate confidenceThe installer for Zoom Workplace VDI Client for Windows contains a vulnerability where cryptographic signatures are not properly verified, allowing an authenticated local user to potentially execute arbitrary code with elevated privileges by tampering with installer components.
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< 6.3.14>= 6.4.10, < 6.4.12CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Verify Zoom VDI Client installationOpen Windows Settings > Apps & Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed applicationsAffected if Zoom Workplace VDI Client or Zoom VDI Client appears in the installed programs list
-
Identify the installed Zoom VDI Client versionIn the same output from the previous step, locate the DisplayVersion field for the Zoom VDI Client entryAffected if The displayed version number is less than 6.3.14, OR greater than or equal to 6.4.10 but less than 6.4.12
-
Confirm the VDI Client variantCheck if the installed product is specifically the VDI/Virtual Desktop Infrastructure variant and not the standard Zoom Workplace Client, as this vulnerability affects only the VDI versionAffected if The product name explicitly includes VDI, Virtual Desktop Infrastructure, or similar VDI designation
-
Assess local user accessVerify that untrusted or low-privilege authenticated users have write access to installer directories (typically C:\Program Files\Zoom or C:\Users\*\AppData\Local\Zoom)Affected if Standard users can modify files in Zoom installation directories, enabling tamper potential
-
Check installer file integrityReview any recently modified .exe or .msi installer files in the Zoom installation directory and compare their digital signatures using 'Get-AuthenticodeSignature filename.exe'Affected if Installer files show invalid, missing, or altered digital signatures
The environment is affected if Zoom Workplace VDI Client for Windows is installed with a version matching less than 6.3.14 or greater than or equal to 6.4.10 but below 6.4.12, and untrusted local users can access installer directories.
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 · scoped6.3.146.4.12
Apply the vendor patch when available and ensure only cryptographically verified, signed installers are used in the VDI environment until the fix is deployed.
6.3.14 or later for 6.3.x branch; 6.4.12 or later for 6.4.x branch
- Identify the currently installed Zoom Workplace VDI Client version from Add/Remove Programs or the Zoom application
- For 6.3.x branch users: Upgrade to version 6.3.14 or later
- For 6.4.x branch users: Upgrade to version 6.4.12 or later
- Download the updated installer from the official Zoom download center at zoom.us
- Run the installer with administrative privileges to apply the update
- Verify the installation completed successfully and confirm the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64740 — 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-2025-64740 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