CVE-2025-0151
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 · uneditedUse after free 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 use-after-free vulnerability exists in certain Zoom Workplace Apps versions. This memory corruption flaw allows an authenticated attacker to exploit freed memory space, potentially achieving privilege escalation through network 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< 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 productCheck Programs and Features on Windows, or Applications folder on macOS, or use 'dpkg -l | grep -i zoom' or 'rpm -qa | grep -i zoom' on Linux to list installed Zoom packagesAffected if Any Zoom product from the affected list is installed (Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, Zoom Meeting SDK, Zoom Workplace VDI)
-
Check Zoom Workplace Desktop versionOpen Zoom app, click your profile picture or Help > About Zoom, or check Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZoomUMX, or run 'zoom --version' if availableAffected if Version is less than 6.3.0
-
Check Zoom Rooms versionOpen Zoom Rooms controller interface, navigate to Settings > Account or Room settings to view version, or check installer on the Rooms PCAffected if Version is less than 6.3.0
-
Check Zoom Rooms Controller versionCheck the controller device (typically a tablet) app version in Settings > About, or check the paired Zoom Rooms versionAffected if Version is less than 6.3.0
-
Check Zoom Meeting SDK versionReview project dependencies or installed package version (check package.json, pom.xml, or equivalent for zoom SDK package version)Affected if SDK version is less than 6.3.0
-
Check Zoom Workplace VDI versionCheck the virtual desktop agent version through the VDI hypervisor console or the installed VDI client on the virtual machineAffected if Version is less than 6.1.16, or between 6.1.17 and 6.2.11 inclusive
You are affected if any Zoom product from the affected list is installed and its version falls below the fixed version thresholds (6.3.0 for most products, or between 6.1.16 and 6.2.11 for VDI).
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 Zoom's published security patches for this vulnerability to all affected Zoom Workplace installations; prioritize systems with network exposure.
Upgrade to version 6.3.0 for Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace products; for VDI, upgrade to 6.1.16+ (if < 6.1.16) or 6.2.12+ (if >= 6.1.17 and < 6.2.12)
- 1. Identify the specific Zoom product in use (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
- 2. Determine the current installed version from the application's About or Settings menu
- 3. For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace: Download and install version 6.3.0 or later from the official Zoom download center
- 4. For Workplace Virtual Desktop Infrastructure: If currently on version < 6.1.16, upgrade to 6.1.16 or later; if currently on version >= 6.1.17 and < 6.2.12, upgrade to 6.2.12 or later; if on version 6.1.16.x or 6.2.12+, no action needed
- 5. Restart the application after upgrade
- 6. Verify the new version is 6.3.0+ (or 6.2.12+ / 6.1.16+ for VDI specifically)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0151 — 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-0151 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