dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2024-39826

MEDIUM · 6.8 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to 5.17.13 / 6.0.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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
Race condition in Team Chat for some Zoom Workplace Apps and SDKs for Windows may allow an authenticated user to conduct information disclosure 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 confidence

A race condition vulnerability in the Team Chat component of Zoom Workplace Apps and SDKs for Windows allows an authenticated user to exploit a timing flaw in the chat functionality, potentially gaining unauthorized access to information via network access. The vulnerability stems from inadequate synchronization in handling concurrent chat operations.

MitigationApply vendor-supplied patches for affected Zoom Workplace versions when available. Until then, limit network exposure and enforce least-privilege access for Team Chat users.

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.0.0
Workplace DesktopApplication
Affected:< 6.0.0
Workplace Virtual Desktop InfrastructureApplication
Affected:< 5.17.13

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 installed Zoom product on Windows
    Open Windows Settings > Apps > Installed apps, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Zoom*'} | Select-Object DisplayName, DisplayVersion
    Affected if No Zoom product is found or the installed product is not one of: Zoom Meeting SDK, Zoom Workplace Desktop, or Zoom Workplace VDI for Windows
  2. Check Zoom Workplace Desktop version
    Open Zoom Desktop Client, click your profile picture > Help > About Zoom. Alternatively, right-click the Zoom icon in taskbar > About. Record the version number shown (e.g., 5.x.x or 6.x.x)
    Affected if The version displayed is below 6.0.0 (for example, 5.17.12 or 5.16.x)
  3. Check Zoom Workplace VDI version
    If using virtual desktop infrastructure, check the installed Zoom VDI client version through the VDI administration console or by opening the client and navigating to Help > About
    Affected if The version displayed is below 5.17.13
  4. Verify Team Chat feature accessibility
    In the Zoom Desktop client, look for the Team Chat tab in the left sidebar, or check if chat functionality is accessible via the Chat icon in the toolbar
    Affected if Team Chat is present and accessible to the authenticated user, making the race condition exploitable

You are affected if you are running Zoom Workplace Desktop below version 6.0.0, Zoom Workplace VDI below version 5.17.13, or Zoom Meeting SDK below version 6.0.0 on Windows, and the Team Chat feature is enabled and accessible to authenticated users.

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 5.17.13 / 6.0.0 or later
Fixed in 5.17.136.0.0
Interim mitigation

Apply vendor-supplied patches for affected Zoom Workplace versions when available. Until then, limit network exposure and enforce least-privilege access for Team Chat users.

Recommended fix High confidence

Meeting SDK: 6.0.0 | Workplace Desktop: 6.0.0 | Workplace VDI: 5.17.13

  1. 1. For Meeting Software Development Kit users: Upgrade to version 6.0.0 or later
  2. 2. For Workplace Desktop users: Upgrade to version 6.0.0 or later
  3. 3. For Workplace Virtual Desktop Infrastructure users: Upgrade to version 5.17.13 or later
  4. 4. Verify the update was successful by checking the application version in Help > About Zoom

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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