Exploited CVEs / VMware / CVE-2020-3952

CVE-2020-3952

VMware vCenter Server Information Disclosure Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-05-03 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Broadcom (VMware) Security Advisories, linked below.

Risk summary

CriticalCISA KEV

9.8

CVSS v3 base

90%

EPSS exploit probability

Critical

Severity

2021-11-03

Added to KEV

2022-05-03 (past due)

CISA due date

Actively exploited VMware vCenter Server vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2021-11-03.

Senserva AI read on CVE-2020-3952 CISA required action Official fix for CVE-2020-3952 Admin questions

Senserva AI Opinion for CVE-2020-3952

The VMware Directory Service in vCenter Server fails to enforce access controls, letting an attacker with network access to port 389 extract sensitive directory information, rated Critical (CVSS 9.8) with a 90 percent EPSS score. vCenter's directory underpins authentication for the virtualization estate, so the disclosed data enables full administrative compromise of vSphere. Exploitation is confirmed, and vCenter should never be reachable from general network segments anyway.

Do this: Patch vCenter Server and restrict port 389 and other vCenter services to a dedicated management network.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2020-3952

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2020-3952, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2020-3952.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2020-3952: VMware vCenter Server Information Disclosure Vulnerability
- Affected: VMware vCenter Server
- Severity: Critical, CVSS v3 9.8; EPSS 30-day exploitation probability 90%
- Added to CISA KEV: 2021-11-03; federal remediation due 2022-05-03
- Ransomware-linked: no
- CISA required action: Apply updates per vendor instructions.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Broadcom (VMware) Security Advisories.

Do this now: Federal remediation deadline 2022-05-03; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 29, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2020-3952

Published: 2021-11-03
Last revised: 2021-11-03
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2021-11-03 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 90.4%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-05-03 (past due).

Apply updates per vendor instructions.

Official fix for CVE-2020-3952

The authoritative fix and affected-version list are published by the vendor. Find the vCenter Server advisory on Broadcom (VMware) Security Advisories.

Broadcom (VMware) Security Advisories CISA KEV entry

Common questions about CVE-2020-3952

Is CVE-2020-3952 actively exploited?

Yes. CVE-2020-3952 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 90%.

What is the CISA deadline and required action for CVE-2020-3952?

CISA set the federal (BOD 22-01) remediation due date at 2022-05-03, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.

What fixes CVE-2020-3952?

The authoritative fix is in the vendor advisory: see Broadcom (VMware) Security Advisories for the patched vCenter Server versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2020-3952?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2020-3952's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited VMware CVEs: CVE-2025-22226 CVE-2025-22224 CVE-2025-22225 CVE-2024-38812 CVE-2024-38813 CVE-2024-37085 CVE-2022-22948 CVE-2023-34048
All VMware exploited CVEs on one page: VMware vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.