CVE-2025-27440
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 · uneditedHeap overflow in some Zoom Workplace Apps may allow an authenticated user to conduct an escalation of privilege 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 · low confidenceHeap overflow vulnerability in Zoom Workplace Apps allowing an authenticated user to escalate privileges via network access. This is a memory corruption vulnerability where improper bounds checking during heap memory operations permits an authenticated attacker to overwrite adjacent memory regions, potentially gaining elevated system privileges.
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.16>= 6.1.17, < 6.2.12CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed Zoom productCheck the installed applications on the system. Look for Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or Zoom Meeting SDK in the installed programs list or application directory.Affected if Any Zoom product from the affected product list is installed
-
Check Zoom Workplace Desktop versionOpen Zoom app, click the profile picture or Help > About Zoom. The version number is displayed in the format like '6.2.x'. Alternatively, check Add/Remove Programs or the application executable properties.Affected if Version is below 6.3.0 (e.g., 6.2.x, 6.1.x, etc.)
-
Check Zoom Rooms or Zoom Rooms Controller versionAccess the Zoom Rooms controller interface or check the application version through the system settings or About section. For Zoom Rooms, go to Rooms > Device Info. For Controller, check the app settings or About page.Affected if Version is below 6.3.0
-
Check Zoom Workplace VDI versionCheck the Zoom Workplace Virtual Desktop Infrastructure installation through the virtual desktop environment or contact the VDI administrator for the installed version number.Affected if Version is 6.1.16, or version is >= 6.1.17 but below 6.2.12 (including 6.1.17 through 6.2.11)
-
Confirm network exposure and authentication contextVerify that the Zoom application has network connectivity and that users authenticate to access it. This vulnerability requires an authenticated user with network access to trigger the heap overflow.Affected if Zoom is network-accessible and users authenticate to use it, which is the default configuration
If any Zoom product from the affected list is installed and its version falls below 6.3.0 (or for VDI, falls into the specific vulnerable ranges), the environment is affected by this CVE.
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.166.2.126.3.0
Apply Zoom's security patches when released; until then, minimize network exposure, enforce least-privilege user accounts, and monitor for suspicious authenticated sessions.
Upgrade to Zoom Workplace 6.3.0 or later (VDI: 6.2.12 or later, or 6.1.16 if on older branch)
- 1. Identify the specific Zoom product in use from the affected list (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
- 2. For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, or Workplace: Upgrade to version 6.3.0 or later
- 3. For Workplace Virtual Desktop Infrastructure: If running >= 6.1.17, upgrade to 6.2.12 or later; if running < 6.1.16, upgrade to 6.1.16 or later or migrate to 6.3.0+
- 4. Verify the upgrade was successful by checking the application version in the Zoom client settings or about menu
- 5. Test that Zoom functionality works normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27440 — 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-27440 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