CVE-2025-0149
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 · uneditedInsufficient verification of data authenticity in some Zoom Workplace Apps may allow an unprivileged user to conduct a denial of service 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 confidenceInsufficient verification of data authenticity in Zoom Workplace Apps allows an unprivileged user to cause denial of service via network access. The vulnerability stems from the application failing to properly validate data received over the network before processing it.
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.0< 6.3.0< 6.3.0< 6.3.0< 6.3.0< 6.1.15>= 6.1.16, < 6.2.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed Zoom productCheck what Zoom application is running on the system. Look for Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or Zoom Meeting SDK in installed programs or running processes.Affected if Any Zoom product from the affected list is installed
-
Check Zoom Workplace Desktop versionOpen Zoom Desktop app, click your profile picture or Help menu, then select About Zoom. Note the version number displayed.Affected if Version is shown as less than 6.3.0
-
Check Zoom Rooms versionOpen Zoom Rooms application, navigate to Settings or About section to view the installed version number.Affected if Version is shown as less than 6.3.0
-
Check Zoom Rooms Controller versionAccess the Zoom Rooms Controller device or app and locate the version information in the Settings or About menu.Affected if Version is shown as less than 6.3.0
-
Check Zoom Workplace VDI versionFor Virtual Desktop Infrastructure deployments, check the version through the VDI admin console or the client application About section.Affected if Version is less than 6.1.15, OR version is 6.1.16 through 6.2.9 (less than 6.2.10)
-
Check Zoom Meeting SDK versionFor developers using the Meeting SDK, check the version number in the project dependencies, SDK documentation, or the compiled library properties.Affected if Version is shown as less than 6.3.0
The environment is affected if any installed Zoom product version falls below 6.3.0 (or for VDI, below 6.1.15 or between 6.1.16 and 6.2.9).
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.156.2.106.3.0
Apply the latest security patches for Zoom Workplace Apps once released. Consider network-level filtering to limit exposure to untrusted network sources until the patch is applied.
6.3.0 or later (for VDI: 6.2.10 or later)
- 1. Open the Zoom desktop client or check the Zoom admin portal
- 2. Navigate to the settings or about section to verify the current version
- 3. For Workplace Desktop: Download and install version 6.3.0 or later from the official Zoom website (zoom.us)
- 4. For Meeting Software Development Kit: Update the SDK package in your application to version 6.3.0 or later
- 5. For Rooms/Room Controller: Access the device admin interface, check for updates, and apply version 6.3.0 or later
- 6. For Workplace VDI: Update the VDI deployment to version 6.2.10 or later (preferably 6.3.0)
- 7. Verify the installed version matches the fixed release after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0149 — 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-0149 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