CISA added four vulnerabilities to the Known Exploited Vulnerabilities catalog on 20 November, all of them on evidence of active exploitation, and all four carry a remediation deadline of 23 November 1 2. The gap between listing and deadline is three days. The vCenter entry is the first one I would raise.
vCenter hands out an administrator session without a password
CVE-2026-123890 is an authentication bypass in the VMware Directory Service, and Broadcom scores it 9.8 3. Mandiant lays out the mechanism: the flaw discloses an SRP-6a session key over DCE/RPC, and a successful attempt establishes an authenticated session as administrator@vsphere.local 4. From there the attacker calls the vmdirdbcp RPC interface to run commands and pull data.mdb off the appliance 4.
The fixed builds cover four branches: 9.1.x below 9.1.1.0200, 9.0.x below 9.0.2.0200, 8.0 below 8.0 U3m, and 5.x below 5.2.5 3. The 7.0 row in the same table points extended-support customers to Broadcom Support instead of a build 3. Broadcom lists no workaround, and the patch cannot go in through vCenter Quick Patch 3. Mandiant ties the exploitation to ARMORY CASTLE, which used a tool called BONESAW against a vCenter server in early September 2026 and scanned for port 2012 on the way in 4.
Two details matter more than the score. This is a different bug from CVE-2026-59309, the vCenter bypass Broadcom fixed earlier in the year, so a system that already took that patch still needs this one 3. Updating also takes the management interfaces offline while the workloads keep running 3, so it needs a maintenance conversation, and three days does not leave room for the next scheduled window.
The part I own is the label on the asset. vCenter rarely shows up in an inventory as the thing that controls the hypervisors; it sits under virtualization, or under whoever built the cluster, or under nothing at all. Naming it that way, and handing over the fixed build numbers so the check becomes a version comparison, puts the right question in front of the team that runs the cluster. The upgrade belongs to them.
Roller deserializes the request before it checks who sent it
CVE-2026-129448 is a 9.8 in Apache Roller, covering 4.0.0 through 6.1.4 and fixed in 6.1.6 5. The XML-RPC endpoint accepts vendor extension types and deserializes them before it authenticates the caller, so an unauthenticated request can reach code execution 5.
Apache’s guidance is worth reading twice. Upgrading to 6.1.6 disables the extension types and rejects XML-RPC requests when the feature is off. If the upgrade has to wait, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart. Turning XML-RPC off in the administration interface does not help, because the vulnerable versions deserialize the request before they read that setting 5. A workaround that skips that detail leaves the bug open.
This is the same root cause as CVE-2026-82384, which listed only 6.1.5 as affected, so the newer record widens the range rather than describing a second bug 5.
Roller is a Java blogging and content engine. It tends to survive as a departmental site or a project wiki that outlived the person who asked for it, so the work starts with finding it. I would look for a servlet container with a Roller context and then ask who still reads it.
Expressway: the advisory said no known exploitation, then CISA listed it
CVE-2026-76466 is a 9.8 in the Cisco Expressway Series database service, and Cisco’s fix shipped on 21 October 6. The advisory describes two failures together: the service relies on persistent cookies, and the client certificate validation does not run when TLS Verify Mode is set to Enabled for clustering. An attacker holding those cookies connects to the database service and invokes specific RPC commands, and a successful exploit executes arbitrary commands as root on the device 6.
The flaw reaches only clustered deployments of Expressway-C and Expressway-E on a vulnerable release 6. X15.5.3 and earlier move to X15.5.20, and X14 and earlier migrate to a fixed release. Cisco lists no workaround 6.
The advisory, published 21 October, states that Cisco PSIRT was not aware of malicious use of the vulnerability at that time 6. CISA listed it on 20 November on evidence of active exploitation 1. Both statements can be true, with a month between them. A vendor’s “not aware” describes what the vendor has seen, not what is happening, so the catalog entry raises the urgency while the version check stays the same work.
SAP NetWeaver is the low score on the list
CVE-2025-42884 scores 6.5, the only one of the four below critical, and it carries the same 23 November deadline 2. SAP describes an unauthenticated attacker injecting JNDI environment properties or supplying a URL used during a JNDI lookup, which reaches an unintended JNDI provider and can disclose or modify information about the server. SAP rates availability impact as none 7.
The record is a year old, published in November 2025, and it reached the catalog on a 2026 listing date 7. Age does not move it down the list when the deadline is shared, but it does change the question. A portal running 7.50 has had a year to take the note, so the useful check is whether the last update landed rather than whether a plan exists.
All four are due the same day, so the ordering only decides which one gets named first in the message I send.
-
Cybersecurity and Infrastructure Security Agency. (2026, November 20). CISA adds four known exploited vulnerabilities to catalog. https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog ↩︎ ↩︎
-
Cybersecurity and Infrastructure Security Agency. (2026, November 20). Known exploited vulnerabilities catalog (catalog version 2026.11.20). https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json ↩︎ ↩︎
-
Rapid7. (2026, November 19). CVE-2026-123890: Critical authentication bypass in VMware vCenter. https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter/ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
-
Google Threat Intelligence Group, & Mandiant. (2026, November 19). ARMORY CASTLE exploits vSphere. Google Cloud Blog. https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere ↩︎ ↩︎ ↩︎
-
National Institute of Standards and Technology. (2026, November 17). CVE-2026-129448 detail. National Vulnerability Database. https://nvd.nist.gov/vuln/detail/CVE-2026-129448 ↩︎ ↩︎ ↩︎ ↩︎
-
Cisco Systems. (2026, October 21). Cisco Expressway Series remote code execution vulnerability (Advisory cisco-sa-vcs-static-cred-hr7EWZ8t). https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
-
National Institute of Standards and Technology. (2025, November 10). CVE-2025-42884 detail. National Vulnerability Database. https://nvd.nist.gov/vuln/detail/CVE-2025-42884 ↩︎ ↩︎