CVE-2025-30666
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 · uneditedNULL pointer dereference in some Zoom Workplace Apps for Windows 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 confidenceThis is a NULL pointer dereference vulnerability in Zoom Workplace Apps for Windows. An authenticated user can trigger the vulnerability via network access, causing the application to crash due to attempting to dereference a NULL pointer, resulting in denial of service.
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.4.0< 6.4.0< 6.4.0< 6.4.0< 6.1.17>= 6.1.18, < 6.2.13>= 6.2.14, < 6.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Zoom Workplace Desktop versionOpen Zoom Desktop app, click your profile picture, then 'Check for Updates' or look in Help > About Zoom. The version number is displayed in the window that opens.Affected if Version is below 6.4.0
-
Check Zoom Rooms versionOn the Zoom Rooms controller or display, sign in and navigate to the Room Settings or About section. Alternatively, check the Zoom Rooms installer or check the version via the Zoom Rooms web portal.Affected if Version is below 6.4.0
-
Check Zoom Rooms Controller versionOpen the Zoom Rooms Controller app on the tablet or device, then look for version information in Settings or About.Affected if Version is below 6.4.0
-
Check Zoom Meeting SDK versionInspect the SDK libraries included in the application that uses the Zoom Meeting SDK. The version is typically documented in the application's dependencies or SDK release notes.Affected if Version is below 6.4.0
-
Check Zoom Workplace VDI versionCheck the installed Zoom Workplace VDI client version through the VDI environment's software inventory, or by opening the Zoom VDI client and viewing About/Version information.Affected if Version falls below 6.1.17, OR between 6.1.18 and 6.2.12 inclusive, OR between 6.2.14 and 6.3.9 inclusive
You are affected if any installed Zoom product (Desktop, Rooms, Rooms Controller, Meeting SDK, or VDI) matches the version ranges above AND the attacker has network access and valid authentication credentials.
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.176.2.136.3.10
Apply the vendor-supplied patch or update Zoom Workplace Apps for Windows to a version that addresses this vulnerability. Ensure all affected installations are identified and remediated.
6.4.0 (or later) for Meeting SDK, Rooms, Rooms Controller, Workplace Desktop; 6.1.17/6.2.13/6.3.10 or later for Workplace VDI
- 1. Identify the specific Zoom product in use from the affected products list (Meeting Software Development Kit, Rooms, Rooms Controller, Workplace Desktop, or Workplace Virtual Desktop Infrastructure)
- 2. Check the current installed version of the Zoom application
- 3. Download the latest version of the affected Zoom product from the official Zoom website (www.zoom.com)
- 4. Close any running Zoom applications
- 5. Install version 6.4.0 or later for Meeting SDK, Rooms, Rooms Controller, and Workplace Desktop products
- 6. For Workplace Virtual Desktop Infrastructure, upgrade to version 6.1.17, 6.2.13, 6.3.10, or later respectively based on the current version branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30666 — 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-30666 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