CVE-2025-49456
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 · uneditedRace condition in the installer for certain Zoom Clients for Windows may allow an unauthenticated user to impact application integrity 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 confidenceA race condition exists in the installer for certain Zoom Clients for Windows that allows a local unauthenticated user to potentially modify application files during the installation process, impacting the application's integrity.
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.4.10< 6.4.5< 6.4.5< 6.4.10< 6.2.15>= 6.3.10, < 6.3.12CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
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 Settings > Apps > Installed apps (or Control Panel > Programs and Features) and search for Zoom. Look for one of these products: Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Workplace Desktop, or Zoom Workplace Virtual Desktop Infrastructure.Affected if One of the listed Zoom products is found on the system
-
Locate the installed Zoom executableFor Zoom Workplace Desktop, the main executable is typically at C:\Users\<username>\AppData\Roaming\Zoom\bin\Zoom.exe. Right-click the executable, select Properties, and view the Details tab to see the Version field.Affected if Version field shows a number less than 6.4.10 for Zoom Workplace Desktop (or less than 6.4.5 for Zoom Rooms/Zoom Rooms Controller, or specific versions for VDI as listed)
-
Check Zoom Rooms versionOpen the Zoom Rooms application or access its settings interface. Navigate to Account Management or Room Settings to view the version number.Affected if Version is less than 6.4.5 for Zoom Rooms or Zoom Rooms Controller
-
Verify Zoom Workplace VDI versionCheck the installed VDI client version by opening the Zoom VDI client and navigating to Help > About, or check the version in Add/Remove Programs.Affected if Version is less than 6.2.15, OR version is >= 6.3.10 and < 6.3.12
-
Confirm product type from registryOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall. Look for Zoom-related entries and note the DisplayName and DisplayVersion values.Affected if Any Zoom product entry shows a version that falls within the affected ranges for that specific product
You are affected if any Zoom product from the list (Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Workplace Desktop, or Zoom Workplace VDI) is installed with a version number that falls within the specified vulnerable 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.2.156.3.126.4.5
Apply the vendor-supplied patch by updating Zoom Client for Windows to the latest version once released, as this is a code-level fix in the installer that cannot be mitigated through configuration changes.
Meeting SDK >= 6.4.10; Rooms >= 6.4.5; Rooms Controller >= 6.4.5; Workplace Desktop >= 6.4.10; Workplace VDI >= 6.2.15 or >= 6.3.12
- Identify which Zoom product(s) are installed from the affected list: Meeting Software Development Kit, Rooms, Rooms Controller, Workplace Desktop, or Workplace Virtual Desktop Infrastructure
- Check the current installed version of the affected Zoom product
- Download the latest version from the official Zoom website (www.zoom.com) or your organization's software distribution channel
- For Meeting Software Development Kit: upgrade to version 6.4.10 or later
- For Rooms: upgrade to version 6.4.5 or later
- For Rooms Controller: upgrade to version 6.4.5 or later
- For Workplace Desktop: upgrade to version 6.4.10 or later
- For Workplace Virtual Desktop Infrastructure: if on 6.2.x, upgrade to 6.2.15 or later; if on 6.3.x, upgrade to 6.3.12 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49456 — 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-2025-49456 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