dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2025-49458

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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
Buffer overflow in certain Zoom Workplace Clients may allow an authenticated 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

A buffer overflow vulnerability exists in certain versions of Zoom Workplace Clients. The flaw allows an authenticated user to trigger a buffer overflow through network access, potentially causing the application to crash and result in a denial of service condition.

MitigationUpdate Zoom Workplace Clients to the latest version provided by Zoom, which contains the fix for this buffer overflow vulnerability.

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.0
Rooms ControllerApplication
Affected:< 6.5.0
Workplace DesktopApplication
Affected:< 6.5.0
RoomsApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 product
    Check the application name and type installed on the system - look for Zoom Meeting SDK, Zoom Rooms Controller, Zoom Workplace Desktop, Zoom Rooms, or Zoom Workplace VDI in installed programs or application metadata.
    Affected if The product matches one of the affected products: Zoom Meeting SDK, Zoom Rooms Controller, Zoom Workplace Desktop, Zoom Rooms, or Zoom Workplace VDI.
  2. Check Zoom Workplace Desktop version
    Open Zoom application, click on your profile picture or initials, then select 'Check for Updates' or 'About Zoom' to view the installed version number. Alternatively, right-click the Zoom icon and select 'Check for Updates' or look in the application settings under 'About' section.
    Affected if The installed version is less than 6.5.0.
  3. Check Zoom Rooms version
    Access the Zoom Rooms controller interface or sign in to the Zoom Rooms web portal and navigate to the Room Management section to view the installed Zoom Rooms version.
    Affected if The installed version is less than 6.5.0.
  4. Check Zoom Rooms Controller version
    Open the Zoom Rooms Controller application on the control device and navigate to the settings or about section to view the version number.
    Affected if The installed version is less than 6.5.0.
  5. Check Zoom Meeting SDK version
    Review the SDK version referenced in your project dependencies or check the SDK library files included in your application deployment.
    Affected if The installed SDK version is less than 6.5.0.
  6. Check Zoom Workplace VDI version
    Check the Zoom Workplace VDI client version through the VDI infrastructure management console or by examining the installed VDI client package version.
    Affected if The version is less than 6.3.14, OR the version is greater than or equal to 6.4.0 but less than 6.4.12.

You are affected if any Zoom product listed above is installed and its version falls within the specified vulnerable ranges.

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 Zoom Workplace Clients to the latest version provided by Zoom, which contains the fix for this buffer overflow vulnerability.

Recommended fix Moderate confidence

6.5.0 for Meeting SDK, Rooms Controller, Workplace Desktop, Rooms; 6.3.14+ or 6.4.12+ for Workplace VDI

  1. 1. Identify the affected Zoom product in use (Meeting SDK, Rooms Controller, Workplace Desktop, Rooms, or Workplace VDI)
  2. 2. Determine the current installed version of the Zoom product
  3. 3. For Meeting SDK, Rooms Controller, Workplace Desktop, and Rooms: Upgrade to version 6.5.0 or later
  4. 4. For Workplace VDI: If using 6.3.x branch, upgrade to 6.3.14 or later; if using 6.4.x branch, upgrade to 6.4.12 or later
  5. 5. Verify the upgrade was successful by checking the new version number
  6. 6. Test that normal Zoom functionality remains operational after the update

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

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49458 — 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-49458 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