Yaamlabs

Vulnerabilities

Zoom Workplace for Windows: patch the critical 9.6 flaw

Zoom bulletin ZSB-26023, CVE-2026-108186, is a critical 9.6 flaw in Zoom Workplace for Windows. What it is, the real risk, and how to get to 7.1.8.

Zoom published two security bulletins on November 10, 2026 for its Workplace desktop client on Windows. The more serious one, ZSB-26023 (CVE-2026-108186), is rated Critical at CVSS 9.6, on the Common Vulnerability Scoring System, the 0 to 10 severity scale, and the fix is to update to version 7.1.8. If you run Zoom Workplace for Windows from 7.1.0 up to 7.1.7, you are in range. The macOS, Linux, Android and iOS builds are not on the affected list, and neither are the VDI client, Zoom Rooms or the Meeting SDK.

No one has exploited this yet. Zoom found the flaw with its own offensive security team, neither CVE is in CISA's Known Exploited Vulnerabilities catalog, and no in-the-wild activity has been reported. The reason to act is the severity and the attack profile: a remote, unauthenticated attacker over the network. A flaw like that on software installed across most of the company deserves the same patch footing as a server-side critical, rather than a wait for the next desktop refresh.

How it works

Zoom's bulletin describes CVE-2026-108186 as improper input validation that lets an unauthenticated user escalate privilege over the network. Improper input validation means the client takes in data and acts on it without first checking that it is well formed and inside the bounds the code expects. Zoom has not published the component, the message type or the exact code path, so the mechanism itself is unknown. The severity instead comes from the CVSS vector Zoom did publish: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.

Each metric tells a defender something. AV:N (network) means the malformed input reaches the client over a network, not from someone already at the keyboard. PR:N (no privileges) means the attacker needs no account on the target. UI:R (user interaction required) is the one caveat: the victim has to do something, such as open content or accept a prompt, for the attack to land, so this is not a silent, wormable push. S:C (scope changed) is why the score reaches 9.6: the impact crosses out of the vulnerable component into the wider system, which on a desktop usually means code or privileges beyond the app's own boundary.

A wording note, because the trackers disagree. Some aggregators label this an authentication bypass. Zoom's own bulletin calls it privilege escalation from improper input validation, and the vendor advisory is the authoritative description. The practical reading lands in the same place: a remote party with no account, given one user action, can gain more on the machine than it should.

What the risk is

There is no incident to hunt for yet. Zoom reports no active exploitation, and nothing has appeared in CISA's Known Exploited Vulnerabilities catalog, the US government list of flaws confirmed to be under attack. The 9.6 score reflects what a working exploit could do, not that one is already circulating.

What makes the clock matter is reach. Zoom Workplace sits on a large share of corporate laptops, it is network-facing by design, and the flaw needs no credentials. Once a reliable exploit exists for a bug this widely installed, the window between disclosure and opportunistic use tends to be short, and the one variable you control is how fast the fleet gets to 7.1.8.

What to do

Update every Windows copy of Zoom Workplace to 7.1.8 or later. One build closes both bulletins: CVE-2026-108187 was addressed in 7.1.5, and 7.1.8 is above that, so a single update covers the pair.

To check a single machine, open Zoom, click your profile picture, and choose Check for updates. The running version also shows under Help, then About Zoom. Compare it against 7.1.8.

Across a fleet, do not depend on users clicking that button. Zoom ships a per-machine MSI installer you can push through Group Policy, Microsoft Intune or Microsoft Configuration Manager. Download the current MSI from Zoom's IT admin download page and deploy 7.1.8. Inventory what is actually installed first: query the installed Zoom version through your endpoint management tool and list every device below 7.1.8, rather than assuming auto-update has already run. Zoom's built-in updater can lag, and managed builds often have it switched off.

The companion flaw, CVE-2026-108187 (ZSB-26024), is an origin validation error rated High at CVSS 8.1, affecting Zoom Workplace for Windows before 7.1.5. It is the same client on the same platform, with the same remote, unauthenticated, user-interaction profile, and a lower impact because its scope does not change. You do not need to track it on its own; shipping 7.1.8 resolves it alongside the critical one.

Patch desktop clients like servers

Desktop software usually sits in a slower patch lane than servers. Auto-update is assumed, there is no maintenance window, and often nobody owns the version number. A network-facing, no-authentication flaw in an app installed on most of the company breaks that assumption. Give the Zoom client, the browser, the VPN agent and the mail client the same thing an internet-facing server gets: a known current version, a view of which endpoints are behind, and a person who pushes the update instead of waiting for it to arrive.

Keeping a live inventory of what is installed and exposed, and closing the gaps for good, is the work behind attack surface management and safeguarding and hardening. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.


Sources: Zoom ZSB-26023 (CVE-2026-108186), Zoom ZSB-26024 (CVE-2026-108187), SmartScope on the two Zoom Workplace for Windows flaws, securityonline.info on CVE-2026-108186, CISA Known Exploited Vulnerabilities catalog.

Back to the blog, or read this post on the full site.