RoomsApplication · Zoom

CVE-2026-30906

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 7.0.0 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
Untrusted search path in the installer for Zoom Rooms for Windows before version 7.0.0 may allow an authenticated user to enable 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

The Zoom Rooms for Windows installer before version 7.0.0 contains an untrusted search path vulnerability, allowing a local authenticated attacker to manipulate the DLL search path and achieve privilege escalation through DLL preloading or hijacking during installation.

MitigationUpdate Zoom Rooms for Windows to version 7.0.0 or later, which contains the corrected installer without the untrusted search path vulnerability.

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:< 7.0.0

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. Confirm Zoom Rooms for Windows is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Zoom Rooms' in the list of installed software
    Affected if Zoom Rooms for Windows appears in the installed programs list
  2. Identify the installed Zoom Rooms version
    In Programs and Features, select Zoom Rooms and view the Version column, or right-click the Zoom Rooms desktop shortcut, select Properties, and check the Details tab for version information
    Affected if The displayed version number is lower than 7.0.0 (for example, 6.x.x or earlier)
  3. Check the installer version used (if available)
    Look in the installation directory (typically C:\Program Files\Zoom Rooms\) for any installer logs or documentation indicating which installer version was used
    Affected if No installer logs or documentation exist, or the installer version referenced is below 7.0.0
  4. Verify if recent installation or upgrade was performed
    Review system event logs (Event Viewer > Windows Logs > Application) for Zoom Rooms installation events, or check the Windows Installer log directory (%TEMP%) for recent ZoomRooms*.log files
    Affected if Installation or upgrade occurred using an installer version prior to 7.0.0

You are affected if Zoom Rooms for Windows is installed with a version lower than 7.0.0, indicating the vulnerable installer was used.

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 7.0.0 or later
Fixed in 7.0.0
Interim mitigation

Update Zoom Rooms for Windows to version 7.0.0 or later, which contains the corrected installer without the untrusted search path vulnerability.

Recommended fix Moderate confidence

Zoom Rooms 7.0.0

  1. Download Zoom Rooms version 7.0.0 or later from the official Zoom website (zoom.us)
  2. Run the Zoom Rooms installer with appropriate administrator privileges
  3. Follow the on-screen prompts to complete the installation of version 7.0.0 or later
  4. Restart the Zoom Rooms service if prompted after installation

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

Fix this in Rooms Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30906 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