Skip to main content
QUIETLYTIC
Active exploitation

CISA flags exploited vCenter, Roller, Expressway and SAP portal flaws

CISA added four exploited flaws to KEV on 20 November: VMware vCenter, Apache Roller, Cisco Expressway and SAP NetWeaver. All carry a 23 November deadline.

Category
Active exploitation
Severity
Critical
CVEs
CVE-2026-123890, CVE-2026-129448, CVE-2026-76466, CVE-2025-42884

CISA put four more actively exploited flaws on its Known Exploited Vulnerabilities (KEV) catalog on 20 November, and the list reads like a tour of the enterprise back office: the directory service inside VMware vCenter, the XML-RPC interface of the Apache Roller blogging server, the database service on Cisco Expressway collaboration gateways, and the SAP NetWeaver Enterprise Portal. Three of the four are rated 9.8, and none of the four requires the attacker to log in. Every entry carries a federal remediation date of 23 November, just three days out, far tighter than the three weeks the catalog most often allows.

Triage order

The four entries share a deadline but not a risk profile. Three come with CISA’s forensic triage flag, which under Binding Operational Directive 26-04 means federal agencies must also check whether the system was breached before the fix landed.

CVE Product CVSS 3.1 Federal due date Forensic triage
CVE-2026-123890 Broadcom VMware vCenter 9.8 23 November Yes
CVE-2026-129448 Apache Roller 4.0.0 to 6.1.4 9.8 23 November Yes
CVE-2026-76466 Cisco Expressway Series 9.8 23 November Yes
CVE-2025-42884 SAP NetWeaver Enterprise Portal 6.5 23 November No

In our assessment the vCenter flaw belongs at the top of the queue. Whoever controls vCenter controls the virtual machines it manages, so a bypass there is a route to the whole estate rather than to one server. The SAP entry is the outlier: a moderate score, no triage requirement, and a fix that has been available for a year.

What the listing does and does not tell us

Inclusion in KEV is itself the confirmation that attackers are using each flaw; CISA’s own data in NVD also records exploitation as active and automatable for all four. The agency has said nothing about who is responsible, which sectors are affected, or when the activity began, and it published no indicators of compromise. For each CVE the catalog marks ransomware use as “Unknown”, which means no link has been confirmed in either direction, not that one has been ruled out.

BOD 26-04 binds only federal civilian agencies. CISA’s alert nonetheless encourages every organisation to take the same risk-based approach to KEV entries, and the directive’s own ordering is a sensible one to borrow: internet-facing assets where exploitation hands over full control come first. Any private-sector team running these products on an exposed network should treat the three-day clock as its own.

The four flaws

VMware vCenter (CVE-2026-123890). The weakness lives in the VMware Directory Service, the identity component vCenter relies on, and lets an unauthenticated attacker who can reach vCenter over the network get past authentication through an alternate path. NVD’s record, which Broadcom supplied, lists fixed builds as 9.1.1.0200 for the 9.1 line, 9.0.2.0200 for 9.0, 8.0 Update 3m for 8.0, and 5.2.5 for the 5.x line. Telco Cloud Platform and Telco Cloud Infrastructure releases that embed vCenter are also affected, and Broadcom points customers of those products to a separate knowledge base article. The CVE was published on 19 November, a day before the KEV listing, so the gap between disclosure and confirmed abuse was close to nil.

Apache Roller (CVE-2026-129448). Roller’s XML-RPC endpoint deserialises vendor extension types before it checks who is sending the request, which gives a remote attacker with no account a path to running code on the server. This CVE widens an earlier one, CVE-2026-82384, which named only 6.1.5 as vulnerable; the new record covers 4.0.0 through 6.1.4 as well, so anyone who ruled themselves out on the strength of the first advisory needs to look again. The Apache project’s record says the bug is being exploited and recommends 6.1.6 or later. Where an upgrade has to wait, the project’s interim measure is to turn off extension handling in the application’s deployment descriptor or drop the XML-RPC servlet mapping entirely, then restart. On older releases the admin-console XML-RPC toggle is no protection, since the dangerous parsing happens before Roller ever reads it.

Cisco Expressway (CVE-2026-76466). CISA files this one as a hard-coded credentials problem in the database service on Expressway Core and Expressway Edge appliances. Cisco’s description in the CVE record ties it to persistent cookies combined with client certificates that go unvalidated on clustered devices: an attacker holding those cookies and able to reach the service can issue commands that run as root on the underlying operating system. The CVE record lists affected releases across the X8, X12, X14 and X15 trains.

SAP NetWeaver Enterprise Portal (CVE-2025-42884). An unauthenticated attacker can supply JNDI environment properties, or a lookup URL, that steer the portal towards a naming provider it should not be using, which can expose or alter information about the server. SAP scores it 6.5 with no availability impact, and the CVE record names the EP-BASIS 7.50 and EP-RUNTIME 7.50 components. SAP’s fix is security note 3660969, and the CVE has been public since 11 November 2025, so a portal that is still exposed has gone a year without it.

Defender actions, in order

  1. Patch vCenter first. Move to the fixed build for your release line, keep the vCenter management interface off any network an attacker could reach, and check Telco Cloud deployments against Broadcom’s separate guidance.
  2. Look for earlier compromise on the triage-flagged products. On vCenter, Roller and Expressway, review authentication logs, administrative account changes, new or unexpected virtual machines, unfamiliar processes and outbound connections from before the fix went on.
  3. Upgrade or isolate Roller. Go to 6.1.6 or later. If that is not possible this week, apply the project’s XML-RPC workaround and confirm the endpoint no longer answers.
  4. Update Expressway clusters. Apply Cisco’s fixed release, limit who can reach the database and clustering services, and treat any session cookies on affected devices as exposed.
  5. Close out the SAP note. Confirm security note 3660969 is applied on every Enterprise Portal instance, starting with any that face the internet.
  6. Retire what cannot be fixed. CISA’s standing instruction is to stop using a product when no mitigation is available.

Frequently Asked Questions

Is VMware vCenter CVE-2026-123890 being exploited? Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026, a day after the CVE was published. CISA has not said who is behind the attacks or which organisations were targeted.

Which vulnerabilities did CISA add to KEV on 20 November 2026? Four: CVE-2026-123890 in VMware vCenter, CVE-2026-129448 in Apache Roller, CVE-2026-76466 in Cisco Expressway and CVE-2025-42884 in SAP NetWeaver Enterprise Portal.

What is the deadline to fix these KEV entries? Federal civilian agencies must remediate all four by 23 November 2026. Other organisations with these products exposed to the internet should work to the same date.

Which Apache Roller versions are affected by CVE-2026-129448? Versions 4.0.0 through 6.1.4 are affected, and 6.1.5 was covered by the earlier CVE-2026-82384. The Apache project recommends upgrading to 6.1.6 or later.


Source: Cybersecurity and Infrastructure Security Agency (CISA). This product uses the NVD API but is not endorsed or certified by the NVD.

Report an error

Found a factual error, an outdated figure, or a broken source link? Let us know and our editorial desk will review it.


Sources

  1. CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog
  2. CISA — Known Exploited Vulnerabilities Catalog
  3. NVD — CVE-2026-123890
  4. NVD — CVE-2026-129448
  5. NVD — CVE-2026-76466
  6. NVD — CVE-2025-42884

Related intelligence


Analyst tools