CVE-2025-58133
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 · uneditedAuthentication bypass in some Zoom Rooms Clients before version 6.5.1 may allow an unauthenticated user to conduct a disclosure of information 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 confidenceZoom Rooms Clients before version 6.5.1 contain an authentication bypass vulnerability that allows unauthenticated users to access sensitive information via network access. An attacker on the network can exploit this flaw without any credentials to disclose confidential data.
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.5.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Zoom Rooms Client versionOpen Zoom Rooms application, navigate to Settings or About section to view the installed version number. Alternatively, check the installed programs list in Control Panel or system package manager for Zoom Rooms version.Affected if Installed version is lower than 6.5.1 (for example, 6.0.0, 6.4.0, 6.5.0, or any version below 6.5.1)
-
Verify Zoom Rooms network service is listeningUse command-line tools such as netstat or ss to list network ports that Zoom Rooms is listening on. Look for ports associated with Zoom Rooms service (typically ports 80, 443, 8000-9000 range for room control interfaces).Affected if Zoom Rooms has open network ports exposed to the local network or untrusted network segments
-
Confirm network access controls are not enforcedReview Zoom Rooms network configuration settings to determine if IP-based access restrictions, firewall rules, or VPN requirements are configured for room access. Check if the web controller interface (typically accessible via browser on the room computer) requires authentication.Affected if Network access controls or authentication requirements for the Zoom Rooms interface are disabled, missing, or set to permissive defaults
You are affected if Zoom Rooms Client version is below 6.5.1 AND the service has network-accessible interfaces without proper authentication controls in place.
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.5.1
Update Zoom Rooms Clients to version 6.5.1 or later to remediate the authentication bypass vulnerability.
6.5.1
- Navigate to the official Zoom download center at www.zoom.com and download Zoom Rooms Client version 6.5.1 or later
- Run the installer on the affected Zoom Rooms machine to apply the update
- After installation, verify the updated version by checking the Zoom Rooms Client version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58133 — 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-58133 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