Workplace DesktopApplication · Zoom
CVE-2025-27439
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 · uneditedBuffer underflow in some Zoom Workplace Apps may allow an authenticated 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 confidenceA buffer underflow vulnerability in Zoom Workplace Apps allows an authenticated user to escalate privileges via network access. The vulnerability stems from improper bounds checking in the application that can be exploited to gain elevated access.
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
< 6.3.0< 6.3.0< 6.3.0< 6.3.0< 6.3.0< 6.1.16>= 6.1.17, < 6.2.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Zoom productOpen Zoom application, go to Help > About Zoom (or zoom.us > Sign In > Account to view installed apps) to see which Zoom product is running: Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or Zoom Workplace VDIAffected if Product is one of: Zoom Workplace Desktop, Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Workplace, or Zoom Workplace VDI
-
Check Zoom Workplace Desktop versionOpen Zoom desktop client, click your profile picture or initials in top right, select Help > About Zoom. Note the version number shown (e.g., 6.2.5)Affected if Version is below 6.3.0 (e.g., 6.2.x, 6.1.x, etc.)
-
Check Zoom Rooms versionOpen Zoom Rooms controller or sign in to Zoom web portal, navigate to Room Management > Zoom Rooms, select the room and view Details to see versionAffected if Version is below 6.3.0
-
Check Zoom Workplace VDI versionConnect to the VDI environment, right-click the Zoom icon and select About, or check version through your virtual desktop infrastructure admin consoleAffected if Version is below 6.1.16, OR version is 6.1.17 through 6.2.11 (6.1.17 <= version < 6.2.12)
-
Confirm authentication is enabledZoom requires an authenticated user account for this exploit. Check if the installation is configured with user authentication (Sign In required) rather than a passcode-only meeting joinAffected if Zoom is configured to allow authenticated users to join meetings or the application requires user sign-in
You are affected if any Zoom product listed above is installed with a version number below the safe thresholds (6.3.0 for most products, or for VDI: below 6.1.16, or between 6.1.17 and 6.2.11).
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.1.166.2.126.3.0
Apply vendor-supplied patches or updates to Zoom Workplace Apps as soon as they become available; verify all installations are running patched versions.
6.3.0 for Workplace Desktop/Meeting SDK/Rooms/Room Controller/Workplace; 6.2.12 or later for Workplace VDI
- Identify the specific Zoom product in use (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
- Determine the currently installed version of the product
- For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, or Workplace: Upgrade to version 6.3.0 or later
- For Workplace Virtual Desktop Infrastructure: If running 6.1.x, upgrade to 6.1.16 or later (but less than 6.2.12), OR upgrade to 6.2.12 or later
- Verify the upgrade was successful by checking the new version number
- Test that all expected functionality works 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
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27439 — 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-27439 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