dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2025-27443

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 6.3.10 / 6.4.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Insecure default variable initialization in some Zoom Workplace Apps for Windows may allow an authenticated user to conduct a loss of 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 confidence

This vulnerability in Zoom Workplace Apps for Windows involves insecure default variable initialization that allows an authenticated local user to achieve loss of integrity. The issue stems from improper handling of variables at startup or during operation, potentially allowing manipulation of application state or data.

MitigationApply the Zoom security update for CVE-2025-27443 by upgrading to the patched version of Zoom Workplace Apps for Windows. Organizations should verify their Zoom client version and deploy the update through standard patch management processes.

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
Meeting Software Development KitApplication
Affected:< 6.3.10
RoomsApplication
Affected:< 6.4.0
Rooms ControllerApplication
Affected:< 6.4.0
Workplace DesktopApplication
Affected:< 6.3.10

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zoom product
    Open Windows Settings > Apps > Installed Apps and look for Zoom-related entries: Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, or Zoom Workplace Desktop (often just called Zoom).
    Affected if Any Zoom product from the affected list is installed.
  2. Check Zoom Workplace Desktop version
    Open the Zoom desktop client, click your profile picture or initials in the top right, then click 'Check for Updates' or look in Help > About Zoom. The version number will be displayed.
    Affected if The version shown is less than 6.3.10.
  3. Check Zoom Rooms version
    Open the Zoom Rooms application or access the Zoom Rooms controller interface. Navigate to Settings or About section to view the version number.
    Affected if The version shown is less than 6.4.0.
  4. Check Zoom Rooms Controller version
    Open the Zoom Rooms Controller app on the designated controller device. Look for version information in the Settings or About screen.
    Affected if The version shown is less than 6.4.0.
  5. Check Zoom Meeting SDK version
    For developers: Check the version of the Zoom Meeting SDK library included in the application by inspecting the SDK DLL files or checking the application's dependencies. The version is typically found in the SDK manifest or file properties.
    Affected if The SDK version is less than 6.3.10.

A user is affected if they have any installed Zoom product (Workplace Desktop, Meeting SDK, Zoom Rooms, or Zoom Rooms Controller) with a version lower than the respective threshold (6.3.10 for Desktop/SDK, 6.4.0 for Rooms/Controller).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.3.10 / 6.4.0 or later
Fixed in 6.3.106.4.0
Interim mitigation

Apply the Zoom security update for CVE-2025-27443 by upgrading to the patched version of Zoom Workplace Apps for Windows. Organizations should verify their Zoom client version and deploy the update through standard patch management processes.

Recommended fix Moderate confidence

Meeting SDK: 6.3.10+ | Rooms: 6.4.0+ | Rooms Controller: 6.4.0+ | Workplace Desktop: 6.3.10+

  1. Identify which Zoom product(s) are in use from: Meeting Software Development Kit, Rooms, Rooms Controller, or Workplace Desktop
  2. For Meeting Software Development Kit: Upgrade to version 6.3.10 or later
  3. For Rooms: Upgrade to version 6.4.0 or later
  4. For Rooms Controller: Upgrade to version 6.4.0 or later
  5. For Workplace Desktop: Upgrade to version 6.3.10 or later
  6. Download the latest version from the official Zoom download center at www.zoom.com
  7. Install the updated version following standard installation procedures
  8. Verify the upgrade was successful by checking the application version in Help > About

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27443 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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