CVE-2025-46788
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 · uneditedImproper certificate validation in Zoom Workplace for Linux before version 6.4.13 may allow an unauthorized user to conduct an 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 · high confidenceImproper certificate validation in Zoom Workplace for Linux allows an unauthenticated attacker to perform man-in-the-middle attacks by spoofing the server's SSL/TLS certificate. This enables interception of sensitive data transmitted between the client and server due to insufficient certificate chain verification.
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.4.13CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Zoom Workplace is installedRun: rpm -qa | grep -i zoom OR dpkg -l | grep -i zoom (depending on package manager)Affected if No Zoom package found means not applicable to this CVE
-
Get installed Zoom versionRun: rpm -qi zoom OR dpkg -s zoom-client (or check /opt/zoom/version.yml)Affected if Unable to determine version - cannot confirm status
-
Compare version to affected rangeIdentify the VERSION field from step 2 and compare numerically to 6.4.13Affected if Version is below 6.4.13 (e.g., 6.4.10, 6.3.0, etc.)
-
Verify SSL/TLS is in useConfirm Zoom is configured to connect to Zoom servers (default behavior) - check network connections while Zoom is running using: ss -tnp | grep zoom OR lsof -i -P | grep -i zoomAffected if Zoom connects to network and transmits data (default behavior)
Environment is affected if Zoom Workplace for Linux is installed with a version lower than 6.4.13 and the client connects to Zoom servers over the network.
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.4.13
Upgrade Zoom Workplace for Linux to version 6.4.13 or later to obtain the proper certificate validation fix.
6.4.13
- 1. Download Zoom Workplace for Linux version 6.4.13 or later from the official Zoom website (https://zoom.us/download)
- 2. Uninstall the current vulnerable version of Zoom Workplace for Linux using your package manager (e.g., sudo apt-get remove zoom or sudo rpm -e zoom)
- 3. Install the downloaded Zoom Workplace for Linux version 6.4.13 or later using your package manager (e.g., sudo apt-get install ./zoom_amd64.deb or sudo rpm -ivh zoom_x86_64.rpm)
- 4. Verify the installed version by running 'zoom --version' or checking the application About section to confirm version 6.4.13 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46788 — 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-46788 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