CVE-2022-22786
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 · uneditedThe Zoom Client for Meetings for Windows before version 5.10.0 and Zoom Rooms for Conference Room for Windows before version 5.10.0, fails to properly check the installation version during the update process. This issue could be used in a more sophisticated attack to trick a user into downgrading their Zoom client to a less secure version.
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 confidenceThe Zoom Client for Meetings and Zoom Rooms for Windows fail to properly validate installation versions during the update process, allowing an attacker to potentially trick users into downgrading to a less secure version. This version check bypass could be leveraged in conjunction with other attacks to compromise endpoints.
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< 5.10.0< 5.10.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check Zoom Meetings version on WindowsOpen Windows Settings > Apps > Apps & features, locate 'Zoom Meetings' in the installed programs list, and note the version number displayed. Alternatively, right-click the Zoom executable (zoom.exe) in the installation directory, select Properties, and view the File version on the Details tab.Affected if The displayed version is lower than 5.10.0 (for example, 5.9.x or earlier)
-
Check Zoom Rooms version on WindowsOpen Windows Settings > Apps > Apps & features, locate 'Zoom Rooms' in the installed programs list, and note the version number displayed. Alternatively, check the Zoom Rooms executable properties in its installation folder.Affected if The displayed version is lower than 5.10.0 (for example, 5.9.x or earlier)
-
Verify version through Zoom applicationLaunch the Zoom application (either Meetings or Rooms client), click on your profile picture or initial in the top-right corner, and select 'Check for Updates' or view the version information in the About/Help section to confirm the installed build number.Affected if The reported version is below 5.10.0
Your environment is affected if either Zoom Meetings or Zoom Rooms for Windows is installed with a version number lower than 5.10.0.
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 · scoped5.10.0
Update Zoom Client for Meetings and Zoom Rooms to version 5.10.0 or later on all Windows endpoints to remediate this vulnerability.
Version 5.10.0 or later for both Zoom Client for Meetings and Zoom Rooms
- Close all running Zoom Client for Meetings or Zoom Rooms applications
- Navigate to the official Zoom download page at zoom.us/download or your organization's software distribution channel
- Download the latest version of the Zoom client for Windows
- Run the Zoom installer executable (.exe)
- Follow the on-screen installation prompts to complete the upgrade
- After installation, launch Zoom and verify the version is 5.10.0 or later by clicking your profile picture and selecting 'Check for Updates' or viewing the version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22786 — 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-2022-22786 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