dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2025-64739

HIGH · 7.5 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 6.3.14 / 6.4.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
External control of file name or path in certain Zoom Clients may allow an unauthenticated user to conduct a disclosure of information via network 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 confidence

This is a path traversal vulnerability in certain Zoom client applications where an unauthenticated attacker can potentially access sensitive files on the affected system via network access by manipulating file paths.

MitigationOrganizations should ensure all Zoom client installations are updated to the latest version once available, and may consider using Zoom's centralized deployment tools to manage and verify client updates across the environment.

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
Meeting Software Development KitApplication
Affected:< 6.5.10
Rooms ControllerApplication
Affected:< 6.5.10
Workplace DesktopApplication
Affected:< 6.5.10
RoomsApplication
Affected:< 6.5.10
Workplace Virtual Desktop InfrastructureApplication
Affected:< 6.3.14>= 6.4.10, < 6.4.12

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify installed Zoom products
    On Windows, open Programs and Features or check C:\Program Files\Zoom and C:\Program Files (x86)\Zoom for Zoom folders. On macOS, check /Applications for Zoom icons. List all Zoom applications present on the system.
    Affected if Any Zoom Meeting SDK, Zoom Rooms Controller, Zoom Workplace Desktop, Zoom Rooms, or Zoom Workplace VDI is installed.
  2. Determine installed version of Zoom products
    For Zoom Workplace Desktop: open the client, click your profile picture, then Help > About Zoom. For Zoom Rooms: access the controller interface or check the room computer's Zoom Rooms app. For SDK versions, check the manifest or version file included with the deployment.
    Affected if The version number is below 6.5.10 for Meeting SDK, Rooms Controller, Workplace Desktop, or Rooms. For Workplace VDI, the version is 6.3.14 or any version from 6.4.10 up to 6.4.11.
  3. Check if client connects to untrusted networks
    Review network connectivity rules and Zoom server configurations. Verify whether the Zoom client is configured to automatically connect to meetings from untrusted sources or if network segmentation is in place.
    Affected if The Zoom client can initiate or accept connections from untrusted network sources without additional verification.
  4. Verify file access paths used by Zoom
    Examine Zoom client logs (typically in %APPDATA%\Zoom or ~/Library/Application Support/Zoom) for any file path operations, especially those involving user-supplied or meeting-server-supplied paths.
    Affected if The Zoom client processes or resolves file paths from network sources without sanitization.

You are affected if any Zoom product from the list is installed and its version falls within the affected ranges: below 6.5.10 for Meeting SDK, Rooms Controller, Workplace Desktop, or Rooms; or exactly 6.3.14, or between 6.4.10 and 6.4.11 for Workplace VDI.

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.

dbcve · scoped
Upgrade available Upgrade to 6.3.14 / 6.4.12 / 6.5.10 or later
Fixed in 6.3.146.4.126.5.10
Interim mitigation

Organizations should ensure all Zoom client installations are updated to the latest version once available, and may consider using Zoom's centralized deployment tools to manage and verify client updates across the environment.

Recommended fix High confidence

6.5.10 for Meeting SDK, Rooms Controller, Workplace Desktop, and Rooms; 6.4.12 or 6.3.14 for Workplace Virtual Desktop Infrastructure

  1. Identify the affected Zoom product(s) installed in your environment
  2. For Meeting Software Development Kit, Rooms Controller, Workplace Desktop, and Rooms: Upgrade to version 6.5.10 or later
  3. For Workplace Virtual Desktop Infrastructure: If running >= 6.4.10, upgrade to 6.4.12 or later; if running < 6.4.10, upgrade to 6.3.14 or later
  4. Verify the upgrade was successful by checking the installed version number
  5. Test that Zoom functionality works as expected post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2025-64739 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