# SZB-0712aed4d5: VMware vCenter flaw CVE-2026-123890 lets network attackers bypass authentication

Broadcom, which owns VMware, said in an advisory that a critical authentication bypass in the VMware Directory Service affects vCenter 8.0, 9.0 and 9.1 and related Cloud Foundation and vSphere Foundation builds, with fixed versions released for all supported branches.

- Type: Early warning
- Kind: Vulnerability
- Vendor: VMware
- Product: vCenter
- Attacker tool: Babuk-derived ransomware
- Threat actor: ARMORY CASTLE, Chinese APT
- Status: Confirmed
- Sources: 5 distinct
- First seen: 2026-11-19 14:24 UTC
- Confirmed: 2026-11-19 15:14 UTC

Written by a model from the sources below. Verify against them.

## Summary

Broadcom, which owns VMware, said in an advisory that a critical authentication bypass in the VMware Directory Service affects vCenter 8.0, 9.0 and 9.1 and related Cloud Foundation and vSphere Foundation builds, with fixed versions released for all supported branches. The company said it has not seen any attacks exploiting the flaw or any public exploit code, and it lists no workaround.

## What to do

- Apply the fixed vCenter version from Broadcom's advisory for your branch as an emergency change.
- Consult your security team on patch timing, since Broadcom rates the issue an emergency change.
- Plan to upgrade vCenter to 9.1.1 first if a VCF 9.1.1 upgrade is in progress, to avoid the Back-in-Time conflict.
- Treat unpatched or end-of-support vCenter systems as exposed, because Broadcom lists no workaround.

## Timeline

- 2026-11-19 14:22 UTC: Made public by Bluesky
- 2026-11-19 14:24 UTC: First seen by cve.now
- 2026-11-19 15:14 UTC: Confirmed as CVE-2026-123890

## Evidence (5 sources)

- 2026-11-19 · Social · [Bluesky](https://bsky.app/profile/securityonline.bsky.social/post/3n2obheyvov2q): “vCenter zero-day CVE-2026-123890 was exploited by ARMORY CASTLE before Broadcom patched it in VMSA-2026-0009.”
- 2026-11-19 · Social · [Mastodon](https://infosec.exchange/@DailyCyberSecurity/117643552392373531): “vCenter zero-day CVE-2026-123890 was exploited by ARMORY CASTLE before Broadcom patched it in VMSA-2026-0009.”
- 2026-11-19 · Social · [Hacker News](https://news.ycombinator.com/item?id=50560544): “Suspected Chinese APT exploited VMware vCenter zero-day to bypass auth”
- 2026-11-19 · Press · [The Hacker News](https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html): “A critical flaw in VMware vCenter lets an attacker with network access bypass authentication and gain unauthorized access to the system, Broadcom, which owns VMware, said in an advisory published today.”
- 2026-11-19 · Social · [Bluesky](https://bsky.app/profile/aiuto-ch.bsky.social/post/3n2oeuhvi4ufx): “Incident Radar | ARMORY CASTLE Exploited VMware vCenter Zero-Day to Create SSO Administrators”

## Corrections

None so far.

Something wrong on this page? Report an error: https://github.com/sazabi/cve.now/issues/new?title=Wrong%20fact%20on%20SZB-0712aed4d5&body=https%3A%2F%2Fcve.now%2FSZB-0712aed4d5%0A%0AWhat%20is%20wrong%2C%20and%20the%20source%20that%20shows%20it%3A%0A

## Questions about VMware vCenter flaw CVE-2026-123890 lets network attackers bypass authentication

### Has VMware confirmed it?

Yes. Confirmed as CVE-2026-123890.

Source: https://bsky.app/profile/securityonline.bsky.social/post/3n2obheyvov2q, https://infosec.exchange/@DailyCyberSecurity/117643552392373531, https://news.ycombinator.com/item?id=50560544, https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html, https://bsky.app/profile/aiuto-ch.bsky.social/post/3n2oeuhvi4ufx

### What should VMware and vCenter users do?

Apply the fixed vCenter version from Broadcom's advisory for your branch as an emergency change. Consult your security team on patch timing, since Broadcom rates the issue an emergency change. Plan to upgrade vCenter to 9.1.1 first if a VCF 9.1.1 upgrade is in progress, to avoid the Back-in-Time conflict. Treat unpatched or end-of-support vCenter systems as exposed, because Broadcom lists no workaround.

### Does it have a CVE?

Yes. It is tracked as CVE-2026-123890, CVE-2026-59309, CVE-2026-59310, CVE-2026-123891 and CVE-2026-123892.

Source: https://cve.now/CVE-2026-123890, https://cve.now/CVE-2026-59309, https://cve.now/CVE-2026-59310, https://cve.now/CVE-2026-123891, https://cve.now/CVE-2026-123892

## Tracked as

- [CVE-2026-123890](https://cve.now/CVE-2026-123890.md)
- [CVE-2026-59309](https://cve.now/CVE-2026-59309.md)
- [CVE-2026-59310](https://cve.now/CVE-2026-59310.md)
- [CVE-2026-123891](https://cve.now/CVE-2026-123891.md)
- [CVE-2026-123892](https://cve.now/CVE-2026-123892.md)

## Related

- Browse: [Early warnings](https://cve.now/early-warnings.md)

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/SZB-0712aed4d5
Site guide for agents: https://cve.now/llms.txt
