dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2026-30900

HIGH · 7.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 6.6.11 or later.
See remediation →
80/100
Remediation priority · High
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
Improper Check of minimum version in update functionality of certain Zoom Clients for Windows may allow an authenticated user to conduct an escalation of privilege via local 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

This is a local privilege escalation vulnerability in Zoom's Windows client update mechanism. The update functionality fails to properly validate minimum version requirements, allowing an authenticated local user to potentially execute code with elevated privileges.

MitigationUpdate Zoom Clients for Windows to the patched version as provided by Zoom. Organizations should ensure all client installations are updated through their patch management processes.

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.6.0, < 6.6.11
Workplace DesktopApplication
Affected:>= 6.6.0, < 6.6.11
Workplace Virtual Desktop InfrastructureApplication
Affected:<= 6.6.10

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify installed Zoom product and version on Windows
    Open Zoom desktop client, click Help > About Zoom to view the version number. Alternatively, check Programs and Features or the Zoom installation directory (typically C:\Users\<username>\AppData\Roaming\Zoom or C:\Program Files\Zoom) for version information.
    Affected if The installed version falls within >= 6.6.0 and < 6.6.11 (for Meeting SDK or Workplace Desktop), or <= 6.6.10 (for Workplace VDI).
  2. Confirm the update mechanism is present
    Verify the Zoom update service or updater component exists. Check for files such as ZoomUpdate.exe, updater.exe, or the ZoomUpdate service in Windows Services (services.msc).
    Affected if The Zoom update service or updater component is installed and enabled on the system.
  3. Check Zoom update service configuration
    Open Windows Services (services.msc) and locate the Zoom service. Verify the service status and startup type. Also check for any scheduled tasks related to Zoom updates (Task Scheduler > Task Scheduler Library > Zoom).
    Affected if The Zoom update service is configured to run, particularly with elevated privileges.

A user is affected if they have Zoom Meeting SDK, Workplace Desktop, or Workplace VDI installed on Windows with a version between 6.6.0 and 6.6.10 (or < 6.6.11 for Desktop/SDK), and the update mechanism is present and operational on the system.

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.6.11 or later
Fixed in 6.6.11
Interim mitigation

Update Zoom Clients for Windows to the patched version as provided by Zoom. Organizations should ensure all client installations are updated through their patch management processes.

Recommended fix High confidence

Upgrade to Zoom version 6.6.11 or later for Meeting SDK, Workplace Desktop, and Workplace VDI

  1. 1. Identify the installed Zoom product (Meeting SDK, Workplace Desktop, or Workplace VDI) and verify the current version number
  2. 2. Download the updated Zoom client version 6.6.11 or later from the official Zoom website (www.zoom.com)
  3. 3. For Workplace Desktop: Run the installer and follow the prompts to complete the upgrade
  4. 4. For Meeting SDK: Update the SDK package in your application to version 6.6.11 or later
  5. 5. For Workplace VDI: Contact your VDI administrator to ensure the Zoom VDI client is updated to version 6.6.11 or later
  6. 6. After updating, restart the Zoom application and verify the version number reflects the fix

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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