dbcve.org
Workplace DesktopApplication · Zoom

CVE-2025-49460

HIGH · 7.5 CVSS v3.1 Published 2025-09-09
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
Uncontrolled resource consumption in certain Zoom Workplace Clients may allow an unauthenticated user to conduct a denial of service 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

Uncontrolled resource consumption in certain Zoom Workplace Clients allows an unauthenticated attacker with network access to trigger excessive resource usage (e.g., memory, CPU, or network connections), causing the client to become unresponsive or crash, resulting in denial of service.

MitigationUpdate affected Zoom Workplace Clients to the vendor-provided patched version; network-level rate limiting or firewall rules may provide interim protection by restricting unauthenticated connections.

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
Workplace DesktopApplication
Affected:< 6.5.0
Meeting Software Development KitApplication
Affected:< 6.5.0
RoomsApplication
Affected:< 6.5.0
Rooms ControllerApplication
Affected:< 6.5.0
WorkplaceApplication
Affected:< 6.5.0
Workplace Virtual Desktop InfrastructureApplication
Affected:< 6.3.14>= 6.4.0, < 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zoom products
    Check for Zoom executables or installed applications: On Windows check Add/Remove Programs or Program Files for 'Zoom' folders; On macOS check /Applications folder; On Linux check /usr/share/zoom or package manager listings
    Affected if Any Zoom product (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, or VDI) is installed
  2. Check Zoom Workplace Desktop version
    Right-click the Zoom executable (zoom.exe on Windows, Zoom.app on macOS), select Properties, go to Details tab to view File Version. On Linux run: zoom --version
    Affected if Version is below 6.5.0 (e.g., 6.4.x, 6.3.x, etc.)
  3. Check Zoom Meeting SDK version
    Inspect the SDK DLL files or check the installed SDK package version through the host application's references or the SDK's manifest file
    Affected if Version is below 6.5.0
  4. Check Zoom Rooms version
    On the Zoom Rooms machine, open Zoom Rooms app, click the profile icon or navigate to Settings > About to view the version number
    Affected if Version is below 6.5.0
  5. Check Zoom Workplace VDI version
    Check the VDI client installation package version or the virtual desktop environment's installed Zoom component version through system information or the VDI admin console
    Affected if Version is below 6.3.14 OR between 6.4.0 and 6.4.11 inclusive

If any installed Zoom product version falls below 6.5.0 (or for VDI, below 6.3.14 or between 6.4.0-6.4.11), the environment is vulnerable to resource exhaustion attacks from unauthenticated network attackers.

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.0 or later
Fixed in 6.3.146.4.126.5.0
Interim mitigation

Update affected Zoom Workplace Clients to the vendor-provided patched version; network-level rate limiting or firewall rules may provide interim protection by restricting unauthenticated connections.

Recommended fix High confidence

Upgrade to version 6.5.0 for most products; for Workplace VDI, upgrade to 6.3.14 (if on 6.3.x) or 6.4.12 (if on 6.4.x)

  1. Identify the affected Zoom product in your environment (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
  2. Note the current installed version of the affected Zoom product
  3. For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace: Upgrade to version 6.5.0 or later
  4. For Workplace Virtual Desktop Infrastructure: If running 6.3.x, upgrade to 6.3.14 or later; if running 6.4.x, upgrade to 6.4.12 or later
  5. Verify the upgrade was successful by checking the new version number
  6. Test that Zoom services start and operate normally after the upgrade

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

Fix this in Workplace Desktop 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-49460 — 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-49460 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