CVE-2025-49459
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 · uneditedMissing authorization in the installer for Zoom Workplace for Windows on ARM before version 6.5.0 may allow an authenticated user to conduct 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 · moderate confidenceMissing authorization check in the Zoom Workplace installer for Windows on ARM allows an authenticated local user to perform privilege escalation before version 6.5.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Windows on ARM architectureRun 'systeminfo' in Command Prompt and look for 'System Type: ARM64-based PC' or check system information under Settings > AboutAffected if System is not ARM64-based (the vulnerability only affects Windows on ARM)
-
Check Zoom Workplace installed versionOpen Windows Settings > Apps > Installed Apps, find Zoom Workplace, and note the version number displayedAffected if Zoom Workplace version is below 6.5.0 on an ARM64 system
-
Locate Zoom installer executableSearch for Zoom installer files (ZoomInstaller*.exe or similar) in Downloads folder, Zoom installation directory, or use 'Get-ChildItem -Path C:\ -Recurse -Filter "*Zoom*Installer*.exe" -ErrorAction SilentlyContinue' in PowerShellAffected if Installer version found is below 6.5.0 (right-click installer > Properties > Details tab to view File Version)
-
Check Windows installer logs for ZoomReview logs in %temp% folder for Zoom installer logs (files starting with 'Zoom' or 'InstallShield' with recent dates)Affected if Log entries show Zoom installer version below 6.5.0 was run
A defender is affected if running Windows on ARM with Zoom Workplace or its installer version below 6.5.0, as an authenticated local user could exploit the missing authorization check in the installer to gain elevated privileges.
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 · scopedUpgrade Zoom Workplace for Windows on ARM to version 6.5.0 or later to obtain the vendor patch.
Zoom Workplace for Windows on ARM version 6.5.0 or later
- 1. Open Zoom application and navigate to the profile picture or click 'Sign In' to access account settings, or right-click the Zoom icon and select 'Check for Updates'
- 2. Alternatively, visit the official Zoom download center at https://www.zoom.us/download and download the latest version for Windows on ARM
- 3. If you need the specific version, ensure you download Zoom Workplace for Windows on ARM version 6.5.0 or later
- 4. Run the installer with appropriate permissions and complete the installation
- 5. After installation, verify the version by going to Zoom's profile settings or help/about section to confirm the installed version is 6.5.0 or higher
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-49459 — 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-49459 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