InfrastructureCritical 9.8In CISA KEVPatch available
CVE-2026-123890
Authentication bypass in VMware vCenter allows administrative takeover.
How scary is it?
updated 22 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
6 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- Yes
Attacks seen in the wild3
CISA lists it as exploited in the wild.
- Yes
On CISA's exploited list (since 20 Nov 2026)3
CISA deadline for US federal agencies: 23 Nov 2026.
Scare-o-meter
Drop everything
Attackers are already on it. Patch now.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run one of these 3 products in an affected versionVMware Telco Cloud Infrastructure / VMware Telco Cloud Platform / VMware VMware vCenter
VMware Telco Cloud Infrastructure: 3.0
VMware Telco Cloud Platform: 3.0, 4.x, 5.0.x, 5.1.x (+1 more)
VMware VMware vCenter: >= 9.1.x and < 9.1.1.0200, >= 9.0.x and < 9.0.2.0200, >= 8.0 and < 8.0 U3m, >= 5.x and < 5.2.5
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines
CISA's required action for this KEV entry, due 23 Nov 2026 for US federal agencies.
Source 3
Recommendation, AI-writtenUpgrade to listed fixed versions immediately; isolate and restrict access until patched.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. vCenter is core enterprise virtualization management; an authentication bypass can enable full admin takeover, VM control and data access across many organizations.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 20 Nov 2026CISA deadline for US federal agencies: 23 Nov 2026unvetted proof-of-concept code on github
- EPSS
- 3.0%chance of exploitation in the next 30 daystop 13% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 19 Nov 2026analysed here 20 Nov 2026
Do first. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines (CISA's required action for this KEV entry)
In the news
Reported by 10 security news and advisory sources since 2026-11-19. Last widely reported 22 Nov 2026.
AI summary of the linked sources, written 22 Nov 2026
An attacker can obtain an authenticated administrator session on VMware vCenter Server.
- Impact
- An attacker can obtain an authenticated administrator session on VMware vCenter Server.
- Ease of exploit
- The flaw is exploitable remotely without authentication; Google GTIG reported that Armory Castle has been exploiting the vCenter zero-day since at least early September.
- Root cause
- An unauthenticated Secure Remote Password (SRP-6a) session key disclosure over Distributed Computing Environment/Remote Procedure Calls (DCE/RPC) that results in authentication bypass.
- Fix
- Install Broadcom fixes for vCenter in versions 9.1.1.0200, 9.0.2.0200, or 8.0 U3m.
Summary written from: helpnetsecurity.com, thehackernews.com, securityweek.com. Other coverage: cybersecuritynews.com, theregister.com, bleepingcomputer.com.
Written by a language model from those pages only, and not updated when they change. It can be wrong: read the sources.
Summary
Impact
Remote authentication bypass of VMware Directory Service enables administrative access to vCenter, VM control, data exfiltration and lateral movement.
Triage
Executive summary (AI-written)
CVE-2026-123890 represents a critical vulnerability in VMware vCenter, posing a severe risk to organizations relying on this infrastructure for virtual machine management. With a CVSS score of 9.8, this flaw allows attackers to bypass authentication mechanisms, potentially granting them administrative access to the vCenter system. The implications of this vulnerability are substantial, as it enables unauthorized control over virtual machines, potential data exfiltration, and unauthorized lateral movement within affected networks. Immediate action is required to mitigate the risks associated with this vulnerability. Organizations are strongly advised to upgrade to the patched versions of VMware vCenter to protect their infrastructure and data integrity. Given the central role of vCenter in enterprise virtualization, failure to address this vulnerability could lead to significant operational disruptions and data breaches, impacting overall business continuity and security posture.
Technical analysis (AI-written)
The CVE-2026-123890 vulnerability is classified with a CVSS score of 9.8, indicating a major security issue in VMware vCenter, specifically affecting versions 9.1.x (below 9.1.1.0200), 9.0.x (below 9.0.2.0200), 8.0 (below 8.0 U3m), and the 5.x series (below 5.2.5). This vulnerability allows for remote authentication bypass in the VMware Directory Service, which can lead to full administrative access to the vCenter environment. The risk associated with this flaw includes the potential for attackers to manipulate virtual machines, exfiltrate sensitive data, and perform lateral movement within the network, greatly increasing the attack surface for organizations. The exploitation of this vulnerability can be executed remotely, without requiring any physical proximity to the hardware, which significantly increases the risk to organizations. Attackers may leverage phishing or social engineering tactics to gain initial access or deploy known exploits targeting the vulnerable versions of vCenter. Due to the complexity of mitigating such issues once an attacker gains administrative privileges, it’s essential for organizations to proactively address this security flaw. Mitigation strategies primarily involve immediate upgrades to the fixed versions released by VMware. The available patches should be prioritized in organizational patch management processes. Additionally, it is recommended to temporarily isolate affected systems from networks and restrict access until the upgrade is fully implemented. Monitoring systems for unusual behaviors and leveraging intrusion detection systems can provide additional layers of security while patching is in progress. Organizations should also consider performing a thorough security assessment post-patching to identify any potential compromises or unauthorized access that may have occurred prior to mitigation. Establishing a robust incident response plan will be crucial should an exploitation occur, enabling quick action to minimize damage. Continuous education around security best practices for administrators can also reduce the risk of such vulnerabilities being exploited in the future.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| VMware Telco Cloud Infrastructure | 3.0Vendor says fixed in: not stated | |
| VMware Telco Cloud Platform | 3.04.x5.0.x5.1.x5.2Vendor says fixed in: not stated | |
| VMware VMware vCenter | >= 9.1.x and < 9.1.1.0200>= 9.0.x and < 9.0.2.0200>= 8.0 and < 8.0 U3m>= 5.x and < 5.2.5Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- VMware vCenter Server 9.1.x (<9.1.1.0200)
- VMware vCenter Server 9.0.x (<9.0.2.0200)
- VMware vCenter Server 8.0 (<8.0 U3m)
- VMware vCenter Server 5.x (<5.2.5)
- VMware Telco Cloud Platform 3.0/4.x/5.0.x/5.1.x/5.2
- VMware Telco Cloud Infrastructure 3.0
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 20 Nov 2026.
- CISA due date
- 23 Nov 2026, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 6 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable yes, technical impact totalAssessed by CISA 19 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- sanMuSec/vcenter-80u3m-patch-download1 stars
- Cyber-BansalAI/vmware-vcenter-20260 stars
- Quaerendir/cve-2026-123890-audit0 stars
- LLCForge/CVE-2026-1238900 stars
and 2 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 19 Nov 2026First proof-of-concept repository on GitHub (unvetted)
- 19 Nov 2026CISA SSVC assessment: exploitation nonesame day later
- 19 Nov 2026Published1 day later
- 20 Nov 2026Added to CISA KEV (exploited in the wild)same day later
- 20 Nov 2026CVE record last updatedsame day later
- 20 Nov 2026Analysed by vulneraibility.comsame day later
- 23 Nov 2026CISA remediation due date (US federal agencies)3 days later
Common questions
Is CVE-2026-123890 being exploited?
Yes. CVE-2026-123890 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-123890?
CVE-2026-123890 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-123890?
Yes. A fix has been recorded for CVE-2026-123890. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-123890 affect?
CVE-2026-123890 affects VMware vCenter Server 9.1.x (<9.1.1.0200), VMware vCenter Server 9.0.x (<9.0.2.0200), VMware vCenter Server 8.0 (<8.0 U3m), VMware vCenter Server 5.x (<5.2.5), and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-123890?
Upgrade to listed fixed versions immediately; isolate and restrict access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- support.broadcom.com /web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Security news coverage and the AI summary of it: the pages linked in that section.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.