CVE-2025-62483
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 removal of sensitive information in certain Zoom Clients before version 6.5.10 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 confidenceImproper removal of sensitive information in certain Zoom Clients before version 6.5.10 allows unauthenticated users to disclose information via network access. The vulnerability involves sensitive data not being properly stripped from network communications or client storage, enabling an attacker with network access to intercept or access this information without authentication.
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.10< 6.5.10< 6.5.10< 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoom productLocate which Zoom product is installed on the system. Check installed programs, executables, or application directories for Zoom Meeting Software Development Kit, Zoom Rooms Controller, Zoom Workplace Desktop, Zoom Rooms, or Zoom Workplace Virtual Desktop Infrastructure.Affected if Any of the five affected Zoom products are installed on the system
-
Check Zoom client versionAccess the installed Zoom application and retrieve its version number (typically via Help > About, or check the executable file properties), or use system commands to query the installed package version.Affected if Version is below 6.5.10 for Meeting SDK, Rooms Controller, Workplace Desktop, or Rooms; OR version is below 6.3.14 for Workplace VDI; OR version is 6.4.10 through 6.4.12 for Workplace VDI
-
Inspect network communicationsUse a network capture tool to monitor outgoing connections from the Zoom client process and examine payload contents for sensitive data that should have been removed or stripped.Affected if Sensitive or private information is present in unencrypted or improperly sanitized network traffic from the Zoom client
A defender is affected if they have any of the specified Zoom products installed with a version below the safe thresholds (6.5.10 for most products, or the specific VDI ranges) and the client transmits sensitive data over the network.
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.126.5.10
Upgrade all Zoom Client installations to version 6.5.10 or later to remediate this vulnerability. Until patching is complete, consider network segmentation and monitoring for unusual access patterns.
Meeting SDK, Rooms Controller, Workplace Desktop, Rooms: upgrade to 6.5.10 or later; Workplace VDI: upgrade to 6.3.14+ or 6.4.12+
- 1. Identify which Zoom product(s) are in use (Meeting SDK, Rooms Controller, Workplace Desktop, Rooms, or Workplace VDI)
- 2. Check the current installed version of the Zoom product
- 3. For Meeting SDK, Rooms Controller, Workplace Desktop, or Rooms: upgrade to version 6.5.10 or later
- 4. For Workplace Virtual Desktop Infrastructure: if on version 6.3.x, upgrade to 6.3.14 or later; if on version 6.4.x, upgrade to version 6.4.12 or later
- 5. Verify the upgrade was successful by checking the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62483 — 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-62483 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