Skip to content

Product

zoom virtual desktop infrastructure vulnerabilities

27 published CVES affecting zoom virtual desktop infrastructure, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
27
Critical
3
High
15
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest zoom virtual desktop infrastructure CVEs

Newest publication first · page 1 of 2

  1. HighCVSS 7.8 EPSS 0.13%

    Improper privilege management in Zoom for Windows, Zoom Rooms for Windows, and Zoom VDI for Windows clients before 5.14.0 may allow an authenticated user to potentially enable an escalation of privilege via local access. Users may potentially utilize higher level system privilege...

  2. HighCVSS 7.5 EPSS 0.52%

    Zoom clients prior to 5.13.5 contain an improper trust boundary implementation vulnerability. If a victim saves a local recording to an SMB location and later opens it using a link from Zoom’s web portal, an attacker positioned on an adjacent network to the victim client could se...

  3. HighCVSS 7.5 EPSS 0.98%

    Zoom for Windows clients before version 5.13.3, Zoom Rooms for Windows clients before version 5.13.5 and Zoom VDI for Windows clients before 5.13.1 contain an information disclosure vulnerability. A recent update to the Microsoft Edge WebView2 runtime used by the affected Zoom cl...

  4. CriticalCVSS 9.6 EPSS 1.5%

    The Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows) before version 5.12.2 is susceptible to a URL parsing vulnerability. If a malicious Zoom meeting URL is opened, the malicious link may direct the user to connect to an arbitrary network address, leading to...

  5. MediumCVSS 6.1 EPSS 0.87%

    The Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows) before version 5.11.0 are susceptible to a URL parsing vulnerability. If a malicious Zoom meeting URL is opened, the malicious link may direct the user to connect to an arbitrary network address, leading t...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.