CVE-2025-62484
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 · uneditedInefficient regular expression complexity in certain Zoom Workplace Clients before version 6.5.10 may allow an unauthenticated user to conduct an escalation of privilege 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 confidenceZoom Workplace Clients prior to version 6.5.10 contain an inefficient regular expression that can be exploited by an unauthenticated attacker via network access to achieve privilege escalation. The ReDoS-like regex vulnerability appears to allow bypassing authentication controls or elevating privileges once triggered.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Zoom Workplace is installedCheck your system for Zoom Workplace client installation. On Windows, look for 'Zoom' in Program Files or Program Files (x86). On macOS, check /Applications for Zoom. On Linux, check standard package locations.Affected if Zoom Workplace client is present on the system
-
Determine the installed Zoom version on WindowsOpen Zoom and navigate to Help > About Zoom, or right-click the Zoom icon in the system tray and select 'Check for Updates' to view the current version number.Affected if The displayed version number is lower than 6.5.10
-
Determine the installed Zoom version on macOSOpen Zoom, then click 'Zoom' in the menu bar and select 'About Zoom' to display the version information.Affected if The displayed version number is lower than 6.5.10
-
Check for Zoom Meeting SDK usage if applicableIf your application embeds or uses the Zoom Meeting SDK, identify the SDK version by checking the SDK library files or dependencies in your project configuration.Affected if The SDK version is lower than 6.5.10
Your environment is affected if Zoom Workplace or Zoom Meeting SDK version is installed and is lower than 6.5.10.
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
Upgrade Zoom Workplace Clients to version 6.5.10 or later to remediate this vulnerability.
6.5.10
- 1. Identify which Zoom product is affected: Meeting Software Development Kit or Workplace.
- 2. Navigate to the official Zoom download center at www.zoom.com
- 3. Download Zoom Workplace Client version 6.5.10 or later (or the corresponding Meeting SDK version 6.5.10)
- 4. Install the updated client following standard installation procedures
- 5. Verify the installed version shows 6.5.10 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62484 — 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-62484 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