CVE-2025-64738
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 · uneditedExternal control of file name or path in Zoom Workplace for macOS before version 6.5.10 may allow an authenticated user to conduct a disclosure of information 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 confidenceA path traversal vulnerability in Zoom Workplace for macOS versions prior to 6.5.10 allows an authenticated local user to manipulate file paths and access sensitive information beyond intended boundaries. The vulnerability stems from insufficient validation of file paths provided to Zoom's local file handling functions.
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.5.10< 6.5.10CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Zoom Workplace version on macOSOpen Zoom app, click Zoom.us in menu bar, then 'About Zoom' to view the version number, or run: defaults read /Applications/Zoom.app/Contents/Info.plist CFBundleVersionAffected if Version shown is below 6.5.10 (for example 6.5.0, 6.4.20, etc.)
-
Confirm operating system is macOSCheck System Settings > About or run: uname -s in TerminalAffected if Operating system is macOS and Zoom version is below 6.5.10
-
Verify local file handling or screen capture sharing is in useCheck Zoom settings under 'Screen Share' or 'Files' tab to see if local file transfer or screen capture recording features are enabled. These utilize the vulnerable local file handling functions.Affected if File transfer or screen capture features are configured and Zoom version is below 6.5.10 on macOS
-
Check for local user authentication on the Zoom clientReview Zoom meeting settings to confirm local user accounts or login credentials are stored or cached on the system for meeting accessAffected if Local authentication is configured and Zoom version is below 6.5.10 on macOS
You are affected if Zoom Workplace Desktop or Zoom Meeting SDK for macOS is installed with a version lower than 6.5.10, especially if local file handling or screen capture features are in use.
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.5.10
Update Zoom Workplace for macOS to version 6.5.10 or later. Organizations should enforce patch management policies to ensure all macOS clients receive the update.
6.5.10
- Open Zoom Workplace for macOS
- Navigate to Zoom.us menu > Check for Updates
- Upgrade to version 6.5.10 or later
- Alternatively, download the latest version from www.zoom.com/download
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64738 — 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-64738 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