VMware vCenter Vulnerability Was a Chinese Spy Tool for Months
A critical VMware vCenter authentication bypass, CVE-2026-123890, was secretly exploited by Chinese hackers for months before Broadcom's patch — it now tops CISA's newest KEV additions.

The U.S. Cybersecurity and Infrastructure Security Agency added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog on November 20, 2026, and the headline entry is a VMware vCenter authentication bypass, CVE-2026-123890, that Google's Mandiant says a China-linked espionage group quietly exploited for more than two months before Broadcom ever shipped a patch. Federal civilian agencies have until November 23 to remediate all four flaws, which also include bugs in Cisco Expressway, SAP NetWeaver and Apache Roller — but any organization running these products, not just U.S. government networks, should treat the deadline as a patch-now signal.
Quick facts: the Nov. 20 KEV additions
- CISA added 4 CVEs to the KEV catalog on Nov. 20, 2026, with a federal remediation due date of Nov. 23, 2026.
- The headline flaw, CVE-2026-123890, is a critical (CVSS 9.8) authentication bypass in VMware vCenter's Directory Service.
- Mandiant says a China-linked group used a custom tool called BONESAW to exploit it as a zero-day starting around early September 2026 — roughly two and a half months before Broadcom's fix shipped.
- Broadcom patched it on Nov. 19, 2026 via VMSA-2026-0009; fixed builds are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, with no workaround for unpatched systems.
- The other three additions: Cisco Expressway hard-coded credentials (CVE-2026-76466), a SAP NetWeaver JNDI injection flaw (CVE-2025-42884), and an Apache Roller deserialization bug (CVE-2026-129448).
What CISA added to the KEV catalog this week
CISA's Known Exploited Vulnerabilities catalog exists to answer one question for defenders: out of the tens of thousands of CVEs published every year, which ones are attackers actually using right now? Binding Operational Directive 22-01 requires U.S. federal civilian agencies to patch any KEV entry by its listed due date, and the catalog has become the de facto patch-priority list for private-sector security teams worldwide, too. On November 20, 2026, CISA added four new entries, all due by November 23:
- CVE-2026-123890 — VMware vCenter Server, authentication bypass using an alternate path or channel
- CVE-2026-76466 — Cisco Expressway Series, use of hard-coded credentials
- CVE-2025-42884 — SAP NetWeaver, improper neutralization of special elements in data query logic (JNDI injection)
- CVE-2026-129448 — Apache Roller, deserialization of untrusted data
Three of the four are rated critical or near-critical, and all four are now confirmed by CISA to have been exploited in the wild, which is the bar for KEV inclusion — the same threshold that triggered last week's Apache Axis KEV addition. The VMware entry is the one with the most alarming backstory, so it's worth unpacking first.
VMware vCenter CVE-2026-123890: the headline flaw
vCenter Server is the central management console that most mid-size and large organizations use to run VMware's vSphere virtualization platform — it's the single pane of glass that controls which administrators can touch which virtual machines, storage and networking across an entire data center. A vCenter compromise is effectively a data-center compromise.
CVE-2026-123890 sits in vCenter's Directory Service, the component that backs vCenter Single Sign-On and holds the identity store for the whole environment. Broadcom rates it CVSS 9.8 out of 10 — the practical ceiling for severity — because it requires no authentication and no user interaction: an attacker with network access to vCenter can bypass login entirely and land an administrator-level session. Broadcom disclosed the flaw and shipped fixes on November 19, 2026 through advisory VMSA-2026-0009, one day before CISA added it to the KEV catalog.
It's the second vCenter authentication-bypass flaw Pandromeda has covered this month — a separate RCE flaw, CVE-2026-59310, was added to KEV on Nov. 1 — but what makes this one different from a routine "patch Tuesday" bug is the timeline Google's Mandiant threat intelligence team has laid out: the China-linked group it tracks had already been exploiting CVE-2026-123890 as an unpatched zero-day since roughly early September 2026, meaning the flaw was in active espionage use for more than ten weeks before a fix existed. Mandiant's reporting describes the attackers using a custom post-exploitation tool it calls BONESAW to create a rogue SSO administrator account and exfiltrate vCenter's directory database — the kind of access that would let an intruder quietly map and later move through virtualized infrastructure at will.
Who else is on the list: Cisco, SAP and Apache
The vCenter bug is the one with a nation-state narrative attached, but the other three products on this KEV batch are just as widely deployed, and each has its own distinct risk profile.
Cisco Expressway (CVE-2026-76466): Cisco disclosed this hard-coded-credentials flaw on October 21, 2026, rating it critical with a CVSS score of 9.8. Expressway is Cisco's edge gateway for secure video and voice collaboration, and clustered Expressway-C and Expressway-E deployments running affected code let an unauthenticated attacker execute commands as root. Cisco says there's no workaround — the only fix is upgrading to X15.5.20 or later, with older X14 systems needing a full migration since no patch exists for that branch.
SAP NetWeaver (CVE-2025-42884): This is the oldest flaw in the batch, originally patched by SAP in November 2025 via SAP Security Note 3660969, more than a year before its KEV addition. It's a JNDI injection vulnerability in SAP NetWeaver Enterprise Portal that can let a remote, authenticated attacker run arbitrary code. Its long gap between patch and KEV listing is a reminder that CISA adds a CVE whenever it confirms active exploitation — even a year-old bug earns a spot the moment evidence of real-world attacks surfaces, which typically means unpatched NetWeaver Enterprise Portal instances are still being targeted today.
Apache Roller (CVE-2026-129448): Roller is an open-source, Java-based blogging platform. The Apache Software Foundation disclosed on November 18, 2026 that this unauthenticated deserialization flaw in Roller's XML-RPC endpoint — rated CVSS 9.8 — was under active exploitation, letting an attacker run arbitrary code without logging in first. It affects Roller 4.0.0 through 6.1.4 (a related CVE, CVE-2026-82384, covers 6.1.5), and Apache says simply disabling XML-RPC in the admin console doesn't help, because the vulnerable deserialization happens before that setting is even checked. The real fix is upgrading to Roller 6.1.6 or later; organizations that can't patch immediately need to edit WEB-INF/web.xml to remove the XML-RPC servlet mapping and restart the application.
The four vulnerabilities at a glance
| CVE | Product | Flaw type | Severity | Fix |
|---|---|---|---|---|
| CVE-2026-123890 | VMware vCenter Server | Authentication bypass (Directory Service) | Critical, 9.8 | vCenter 9.1.1.0200 / 9.0.2.0200 / 8.0 U3m |
| CVE-2026-76466 | Cisco Expressway Series | Hard-coded credentials → root RCE | Critical, 9.8 | Upgrade to X15.5.20+ (X14 needs migration) |
| CVE-2025-42884 | SAP NetWeaver Enterprise Portal | JNDI injection | Medium, ~6.5–6.9 | SAP Security Note 3660969 |
| CVE-2026-129448 | Apache Roller | Unauthenticated deserialization | Critical, 9.8 | Upgrade to Roller 6.1.6+ |
Why KEV status matters even after a patch already exists
A common misunderstanding — covered in more depth in our guide to zero-day vulnerabilities — is that CISA's KEV catalog is a list of unpatched bugs. It isn't — most KEV entries, including three of these four, already had vendor fixes available before CISA added them. KEV status is instead a confirmation that real attackers, not just researchers in a lab, are actively using the flaw against real victims. That distinction matters because organizations patch thousands of CVEs a year and have to triage; a KEV listing is CISA's way of saying "stop deprioritizing this one — it's not theoretical." The SAP NetWeaver entry on this list, patched over a year ago, is the clearest example: it sat unlisted until CISA confirmed ongoing exploitation, which is the signal that unpatched NetWeaver Enterprise Portal instances are still a live target today, not a historical footnote.
Who has to patch, and by when
Binding Operational Directive 22-01 legally requires U.S. federal civilian executive branch agencies to remediate every KEV entry by its due date — November 23, 2026 for all four of these. State, local and tribal governments, critical infrastructure operators and private businesses aren't bound by the directive, but CISA explicitly recommends they follow the same prioritization, and security vendors widely treat the KEV due date as the de facto industry deadline. If your organization runs vCenter, Expressway, NetWeaver Enterprise Portal or Roller, the practical answer is the same regardless of sector: patch this week, not on your normal monthly cycle.
How to check exposure and patch each product
- VMware vCenter: Check your build number against Broadcom's VMSA-2026-0009 advisory and update to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. There is no workaround — if you can't patch immediately, restrict network access to the vCenter management interface as a stopgap, and review Directory Service logs for unexpected SSO administrator account creation.
- Cisco Expressway: Confirm whether your deployment is clustered (the primary risk path) and upgrade Expressway-C/E to X15.5.20 or later. X14 deployments have no fix and need to migrate to a supported release.
- SAP NetWeaver: Apply SAP Security Note 3660969 on any NetWeaver Enterprise Portal system (EP-BASIS/EP-RUNTIME 7.50) that hasn't already been patched, and review JNDI-related configuration as SAP recommends.
- Apache Roller: Upgrade to 6.1.6 or later. If an immediate upgrade isn't possible, remove the XML-RPC servlet mapping from
WEB-INF/web.xmland restart — disabling XML-RPC through the admin UI alone does not close the hole.
Bottom line
This batch is a reminder that KEV additions aren't just paperwork for federal IT shops — the vCenter entry alone describes a nation-state group with roughly ten weeks of undetected access inside victim environments before a patch existed. If your organization runs any of these four products, the safest assumption is that you can no longer treat them as "patch when convenient." Verify your version, apply the fix, and — for vCenter in particular — check your Directory Service and SSO logs for anything that looks like it wasn't you.
Frequently asked questions
What is CVE-2026-123890?
It's a critical (CVSS 9.8) authentication bypass in VMware vCenter Server's Directory Service that lets an unauthenticated, remote attacker obtain an administrator-level session. Broadcom patched it on November 19, 2026, and CISA added it to the Known Exploited Vulnerabilities catalog the next day after Google's Mandiant reported it had been exploited as a zero-day since early September 2026.
Was VMware vCenter actually exploited before the patch existed?
Yes, according to Mandiant. The threat intelligence team attributes exploitation to a China-linked group that used a custom tool called BONESAW to create rogue administrator accounts and copy vCenter's directory database, starting roughly two and a half months before Broadcom shipped a fix.
What is the CISA KEV catalog deadline for these vulnerabilities?
CISA set November 23, 2026 as the remediation due date for all four CVEs added on November 20: the VMware vCenter, Cisco Expressway, SAP NetWeaver and Apache Roller flaws. That deadline is binding only for U.S. federal civilian agencies, but CISA recommends every organization treat it as a priority patch window.
Is there a workaround if I can't patch VMware vCenter right away?
Broadcom states there is no workaround for CVE-2026-123890. The only fix is upgrading to vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. If you can't patch immediately, restrict network access to vCenter's management interfaces and monitor Directory Service and SSO logs for signs of unauthorized administrator accounts.
Does disabling XML-RPC protect Apache Roller from CVE-2026-129448?
No. Apache says the vulnerable deserialization happens before Roller checks whether XML-RPC is enabled, so toggling it off in the admin console does not close the hole. The real fix is upgrading to Roller 6.1.6 or later; as an interim step, remove the XML-RPC servlet mapping directly from WEB-INF/web.xml and restart the application.
How is this different from the VMware vCenter flaw Pandromeda covered earlier this month?
That was a separate vulnerability, CVE-2026-59310, a vCenter Syslog server directory-traversal bug disclosed in a different Broadcom advisory. CVE-2026-123890 is a distinct authentication-bypass flaw in vCenter's Directory Service, disclosed and patched weeks later, and it's the one now confirmed to have been actively exploited as a zero-day.
Sources
- CISA: Known Exploited Vulnerabilities Catalogcisa.gov
- NVD: CVE-2026-123890 recordnvd.nist.gov
- VMware Security Response Center blogblogs.vmware.com
- Cisco Security Advisory: Expressway static credential vulnerabilitysec.cloudapps.cisco.com
- NVD: CVE-2026-129448 record (Apache Roller)nvd.nist.gov
- NVD: CVE-2025-42884 record (SAP NetWeaver)nvd.nist.gov
Frequently asked questions
What is CVE-2026-123890?
It's a critical (CVSS 9.8) authentication bypass in VMware vCenter Server's Directory Service that lets an unauthenticated, remote attacker obtain an administrator-level session. Broadcom patched it on November 19, 2026, and CISA added it to the Known Exploited Vulnerabilities catalog the next day after Google's Mandiant reported it had been exploited as a zero-day since early September 2026.
Was VMware vCenter actually exploited before the patch existed?
Yes, according to Mandiant. The threat intelligence team attributes exploitation to a China-linked group that used a custom tool called BONESAW to create rogue administrator accounts and copy vCenter's directory database, starting roughly two and a half months before Broadcom shipped a fix.
What is the CISA KEV catalog deadline for these vulnerabilities?
CISA set November 23, 2026 as the remediation due date for all four CVEs added on November 20: the VMware vCenter, Cisco Expressway, SAP NetWeaver and Apache Roller flaws. That deadline is binding only for U.S. federal civilian agencies, but CISA recommends every organization treat it as a priority patch window.
Is there a workaround if I can't patch VMware vCenter right away?
Broadcom states there is no workaround for CVE-2026-123890. The only fix is upgrading to vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. If you can't patch immediately, restrict network access to vCenter's management interfaces and monitor Directory Service and SSO logs for signs of unauthorized administrator accounts.
Does disabling XML-RPC protect Apache Roller from CVE-2026-129448?
No. Apache says the vulnerable deserialization happens before Roller checks whether XML-RPC is enabled, so toggling it off in the admin console does not close the hole. The real fix is upgrading to Roller 6.1.6 or later; as an interim step, remove the XML-RPC servlet mapping directly from WEB-INF/web.xml and restart the application.
How is this different from the VMware vCenter flaw Pandromeda covered earlier this month?
That was a separate vulnerability, CVE-2026-59310, a vCenter Syslog server directory-traversal bug disclosed in a different Broadcom advisory. CVE-2026-123890 is a distinct authentication-bypass flaw in vCenter's Directory Service, disclosed and patched weeks later, and it's the one now confirmed to have been actively exploited as a zero-day.
Sources
- CISA: Known Exploited Vulnerabilities Catalogcisa.gov
- NVD: CVE-2026-123890 recordnvd.nist.gov
- VMware Security Response Center blogblogs.vmware.com
- Cisco Security Advisory: Expressway static credential vulnerabilitysec.cloudapps.cisco.com
- NVD: CVE-2026-129448 record (Apache Roller)nvd.nist.gov
- NVD: CVE-2025-42884 record (SAP NetWeaver)nvd.nist.gov
Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.
