CVE-2025-49457
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 · uneditedUntrusted search path in certain Zoom Clients for Windows may allow an unauthenticated user to conduct an escalation of privilege via network 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 confidenceThis is an untrusted search path vulnerability in Zoom Clients for Windows where the application loads DLLs or other resources from locations that an attacker can control, potentially allowing injection of malicious code. An unauthenticated attacker with network access can exploit this to achieve privilege escalation on affected Windows systems running Zoom client.
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.3.10< 6.3.10< 6.3.10< 6.3.10< 6.1.16>= 6.2.10, < 6.2.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
- 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.
-
Identify installed Zoom productOpen Windows Settings > Apps > Installed Apps (or Control Panel > Programs and Features) and look for Zoom-related entries such as 'Zoom Workplace Desktop', 'Zoom Rooms', 'Zoom Meeting SDK', or 'Zoom Rooms Controller'Affected if Any Zoom product from the affected list is installed
-
Determine installed version numberRight-click the Zoom application in the Apps list, select 'Advanced options' or 'Properties', and note the Version field. Alternatively, locate the Zoom executable (typically in C:\Users\[User]\AppData\Zoom\bin or C:\Program Files\Zoom), right-click the .exe file, and view the File Properties version detailsAffected if The version cannot be determined or is lower than 6.3.10 for Meeting SDK, Rooms, Rooms Controller, or Workplace Desktop; or is lower than 6.1.16 / between 6.2.10-6.2.11 for Workplace VDI
-
Compare version against CVE-affected rangesIf installed version is 6.3.10 or higher for Meeting SDK, Rooms, Rooms Controller, or Workplace Desktop, the version is patched. For Workplace VDI, check if version is 6.1.16 or higher, or 6.2.12 or higherAffected if Installed version is below 6.3.10 (for Meeting SDK, Rooms, Rooms Controller, Workplace Desktop) OR below 6.1.16 OR between 6.2.10-6.2.11 inclusive (for Workplace VDI)
-
Check if Zoom runs from network or shared driveInspect the directory from which the Zoom executable is launched. If the Zoom installation folder or the working directory is on a network share (\\server\share) or an untrusted local directory with broad write permissions, the vulnerability condition is more likely exploitableAffected if Zoom is launched from or installed on a network share, external drive, or directory where untrusted users can place malicious DLLs
You are affected if a vulnerable Zoom product version is installed (below 6.3.10 for most products, or the specific VDI ranges) AND the client runs from a location where an attacker could place malicious DLLs.
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.1.166.2.126.3.10
Organizations should update affected Zoom Clients for Windows to the latest version once available. Users should avoid running Zoom from network shares or untrusted directories and ensure their installation is current.
Meeting SDK, Rooms, Rooms Controller, Workplace Desktop: upgrade to 6.3.10 or later; Workplace VDI: upgrade to 6.1.16+/6.2.12+
- 1. 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
- 2. Determine the current installed version of the affected Zoom product
- 3. For Meeting Software Development Kit, Rooms, Rooms Controller, or Workplace Desktop: upgrade to version 6.3.10 or later
- 4. For Workplace Virtual Desktop Infrastructure: if using major version 6.1, upgrade to 6.1.16 or later; if using major version 6.2, upgrade to 6.2.12 or later
- 5. Verify the upgrade was successful by confirming the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49457 — 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-49457 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