CVE-2026-30902
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 · uneditedImproper Privilege Management in 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 confidenceImproper Privilege Management vulnerability in certain Zoom Clients for Windows allows an authenticated local user to escalate privileges. The vulnerability stems from insufficient access control mechanisms within the Zoom client software, enabling a user with standard Windows account access to gain elevated (administrator) privileges on the local system.
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.6.0< 6.6.0>= 6.4.0, < 6.4.15>= 6.5.0, < 6.5.13>= 6.6.0, < 6.6.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoom productOpen Windows Control Panel > Programs and Features, or check C:\Program Files\Zoom or C:\Program Files (x86)\Zoom for Zoom executables. Look for 'Zoom Rooms', 'Zoom Workplace Desktop', or 'Zoom Workplace VDI' in the program name.Affected if Any Zoom client for Windows is installed
-
Determine Zoom version numberIn Zoom client, click your profile picture > Settings > About, or right-click Zoom.exe in Program Files and select Properties > Details to view File Version.Affected if Version cannot be determined or is below affected ranges
-
Compare desktop client version against affected rangesIf using Zoom Workplace Desktop (non-VDI), compare your version to < 6.6.0. If version is lower, you are affected.Affected if Version is less than 6.6.0 for Zoom Workplace Desktop
-
Compare Zoom Rooms version against affected rangesIf using Zoom Rooms, compare your version to < 6.6.0. If version is lower, you are affected.Affected if Version is less than 6.6.0 for Zoom Rooms
-
Compare VDI client version against affected rangesIf using Zoom Workplace VDI, compare version to: >= 6.4.0 and < 6.4.15; OR >= 6.5.0 and < 6.5.13; OR >= 6.6.0 and < 6.6.10. Any of these ranges indicate vulnerability.Affected if Version falls into any of the three vulnerable VDI ranges
Your environment is affected if any Zoom client for Windows (Rooms, Workplace Desktop, or Workplace VDI) is installed with a version that falls below 6.6.0 (Desktop/Rooms) or within the specified VDI ranges.
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.4.156.5.136.6.0
Apply the vendor-supplied security patch by updating affected Zoom Client for Windows installations to the latest patched version. Organizations should inventory deployed Zoom versions, prioritize updates for systems with local users, and verify successful patching through endpoint management tooling.
Rooms: 6.6.0+ | Workplace Desktop: 6.6.0+ | Workplace VDI: 6.4.15+, 6.5.13+, or 6.6.10+
- 1. Identify which Zoom product is installed (Rooms, Workplace Desktop, or Workplace Virtual Desktop Infrastructure)
- 2. Check current installed version by opening the Zoom client and navigating to the version information (typically in Help > About)
- 3. For Rooms and Workplace Desktop users: Download and install version 6.6.0 or later from the official Zoom website (zoom.us)
- 4. For Workplace VDI users: Determine your current VDI version (6.4.x, 6.5.x, or 6.6.x) and upgrade to the corresponding fixed version: 6.4.15 or higher, 6.5.13 or higher, or 6.6.10 or higher
- 5. Verify the upgrade was successful by checking the version number again after installation
- 6. Restart the Zoom client to ensure all components are updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30902 — 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-2026-30902 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