dbcve.org
RoomsApplication · Zoom

CVE-2026-30901

HIGH · 7.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 6.6.5 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 Input Validation in Zoom Rooms for Windows before 6.6.5 in Kiosk Mode 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 · high confidence

Improper input validation in Zoom Rooms for Windows in Kiosk Mode allows an authenticated local user to bypass kiosk restrictions and escalate privileges. The vulnerability exists because the Kiosk Mode interface does not properly sanitize or validate user inputs, enabling escape from the locked-down environment.

MitigationUpdate Zoom Rooms for Windows to version 6.6.5 or later to address the input validation flaw.

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
RoomsApplication
Affected:< 6.6.5

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. Verify Zoom Rooms for Windows is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed applications. Look for 'Zoom Rooms' in the list.
    Affected if Zoom Rooms for Windows is not present on the system - the vulnerability does not apply.
  2. Check the installed Zoom Rooms version
    In Zoom Rooms, click the user icon > Settings > About, or right-click the Zoom Rooms shortcut > Properties > Details tab. Alternatively, check the version in Windows Settings > Apps > Apps & features under Zoom Rooms.
    Affected if The installed version is less than 6.6.5 - the vulnerability may be present.
  3. Determine if Kiosk Mode is enabled
    Open Windows Settings > Accounts > Family & other users. Look for kiosk account configurations. In Zoom Rooms, check Settings > Advanced > Kiosk Mode to see if it is turned on. Also check Windows Settings > Lock screen > Screen saver settings for kiosk-related configurations.
    Affected if Kiosk Mode is disabled - the vulnerability cannot be exploited as the attack surface does not exist.
  4. Confirm the combined vulnerability condition
    Review all collected information: if Zoom Rooms for Windows is installed, the version is below 6.6.5, and Kiosk Mode is actively enabled, the environment is vulnerable to this privilege escalation.
    Affected if All three conditions are true: Zoom Rooms for Windows installed + version < 6.6.5 + Kiosk Mode enabled.

A system is affected only if Zoom Rooms for Windows is installed with Kiosk Mode enabled on a version prior to 6.6.5, which allows a local authenticated user to escape kiosk restrictions and escalate privileges.

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.5 or later
Fixed in 6.6.5
Interim mitigation

Update Zoom Rooms for Windows to version 6.6.5 or later to address the input validation flaw.

Recommended fix Moderate confidence

6.6.5

  1. Verify current Zoom Rooms for Windows version via Settings > About
  2. Download Zoom Rooms installer version 6.6.5 or later from the official Zoom download center (zoom.us)
  3. Execute the installer with appropriate administrative privileges
  4. Follow the on-screen prompts to complete the upgrade
  5. Restart the Zoom Rooms service or system as required
  6. Confirm the installed version is 6.6.5 or higher via Settings > About

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rooms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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