dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2025-30669

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 6.3.14 / 6.4.12 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
Improper certificate validation in certain Zoom Clients may allow an unauthenticated user to conduct a disclosure of information via adjacent 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

Improper certificate validation in Zoom client software allows an unauthenticated attacker on the adjacent network to potentially perform a man-in-the-middle attack and disclose information due to inadequate validation of SSL/TLS certificates.

MitigationUpdate affected Zoom client installations to the patched version provided by Zoom. Enforce certificate validation policies and monitor for network-based interception attempts on the adjacent segment.

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.5.10
Workplace DesktopApplication
Affected:< 6.5.10
Workplace Virtual Desktop InfrastructureApplication
Affected:< 6.3.14>= 6.4.10, < 6.4.12

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed Zoom product
    Check if Zoom Meeting SDK, Zoom Workplace Desktop, or Zoom Workplace VDI is installed. On Windows, look in Add/Remove Programs or check Program Files for Zoom folders. For SDK, check the application's dependencies or installed components.
    Affected if Any of the three affected products is installed (Meeting SDK, Workplace Desktop, or Workplace VDI)
  2. Check Zoom Workplace Desktop version
    Open Zoom desktop client, click your profile picture, then 'Check for Updates' or go to Help > About Zoom. The version number displays in the format x.x.x.
    Affected if Version is less than 6.5.10
  3. Check Zoom Meeting SDK version
    Check the application's documentation, dependencies, or the SDK version file included in the deployment. Common locations: the SDK's version.txt or in the application's assembly info.
    Affected if Version is less than 6.5.10
  4. Check Zoom Workplace VDI version
    Open the VDI client session, check the About or Version information in the client interface, or query the virtual desktop's installed software inventory.
    Affected if Version is less than 6.3.14 OR version is 6.4.10 through 6.4.11 inclusive

A user is affected if they have any of the three Zoom products installed and the installed version falls below the patched version for their specific product (6.5.10 for SDK and Desktop, 6.3.14 or 6.4.12 for VDI depending on branch).

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.14 / 6.4.12 / 6.5.10 or later
Fixed in 6.3.146.4.126.5.10
Interim mitigation

Update affected Zoom client installations to the patched version provided by Zoom. Enforce certificate validation policies and monitor for network-based interception attempts on the adjacent segment.

Recommended fix High confidence

Meeting SDK 6.5.10+, Workplace Desktop 6.5.10+, Workplace VDI 6.3.14+ or 6.4.12+

  1. 1. Identify which Zoom product(s) are in use (Meeting SDK, Workplace Desktop, or Workplace Virtual Desktop Infrastructure)
  2. 2. Check the current installed version of the affected Zoom product
  3. 3. For Meeting Software Development Kit: upgrade to version 6.5.10 or later
  4. 4. For Workplace Desktop: upgrade to version 6.5.10 or later
  5. 5. For Workplace Virtual Desktop Infrastructure: upgrade to version 6.3.14 or later, or version 6.4.12 or later if using 6.4.x branch
  6. 6. Verify the upgrade was successful by confirming the new version is running

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30669 — 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-30669 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