Skip to main content
株式会社オブライト
株式会社オブライト

Cisco Expressway CVE-2026-76466 + 5 more

Vulnerability Digest Nov 21, 2026

Published 2026/11/2112 min read

Cisco Expressway CVE-2026-76466 (CVSS 9.8) is exploited and in CISA KEV: update clustered units to X15.5.20. Also Apache Roller, SAP, vCenter, Mitel, TeamCity

From the information published or updated on November 20-21, we picked the items most relevant to small and midsize business systems. The top priority is Cisco Expressway (CVE-2026-76466). Cisco rates it CVSS v3.1 9.8 (Critical). On clustered Expressway-C and Expressway-E devices, an unauthenticated attacker may be able to run OS commands as root. Cisco's advisory lists no workaround. At publication on October 21, Cisco said it was not aware of exploitation. However, the security firm F6 reported on November 18 an attack on a real device after a public PoC (proof-of-concept code) appeared, and CISA added the flaw to its KEV (Known Exploited Vulnerabilities) catalog on November 20. If you run clustered Expressway devices, updating to X15.5.20 is the top priority.

The other top priority is the blog software Apache Roller (CVE-2026-129448). It may allow code execution without authentication, Apache states it is being exploited, and it was also added to KEV. Updating to 6.1.6 or later is required. SAP NetWeaver Enterprise Portal (CVE-2025-42884) and VMware vCenter (CVE-2026-123890) were also added to KEV on November 20. vCenter was covered in yesterday's article, so this time we add only the new fact, the KEV listing. In this article, "confirmed exploited" means listed in CISA KEV, or exploitation stated by the vendor or a primary source. Today there are four confirmed-exploited items, and the KEV due date for all four is November 23. We also cover critical flaws in Mitel MiCollab (CVSS 10.0) and JetBrains TeamCity (CVSS 9.8); the sources we checked do not mention exploitation of these two.

Today's vulnerability list

ProductCVESeverity (CVSS)ExploitationFix
Cisco Expressway (clustered)CVE-2026-764669.8 (v3.1, Cisco)Confirmed exploited (F6 reported an attack; added to KEV Nov 20; Cisco's advisory did not report exploitation at publication)X15.5.20. Migrate from X14 and earlier. No workaround
Apache RollerCVE-2026-1294489.8 (v3.1, Apache)Confirmed exploited (stated by Apache; added to KEV Nov 20)6.1.6 or later; configuration change if you cannot upgrade
SAP NetWeaver Enterprise PortalCVE-2025-428846.5 (v3.1, SAP)Confirmed exploited (added to KEV Nov 20)SAP Security Note 3660969
VMware vCenterCVE-2026-1238909.8 (v3.1, Broadcom/NVD)Confirmed exploited (added to KEV Nov 20; also reported by Mandiant/GTIG)9.1.1.0200 / 9.0.2.0200 / 8.0 U3m / VCF 5.2.5. No workaround
Mitel MiCollab (AWV)CVE-2026-133323 (Mitel ID MTLVULN-1864)10.0 (v3.1)No exploitation reportedPatch in Mitel KB000129195, or a newer release
JetBrains TeamCityCVE-2026-1328919.8 (v3.1, JetBrains)No exploitation reported2026.2 / 2026.1.4 / 2025.11.8

Cisco Expressway CVE-2026-76466 — Unauthenticated root command execution on clustered devices

What happens. Expressway is a Cisco appliance used for connections such as external video conferencing (Expressway-C on the inside, Expressway-E on the outside). A flaw in its database service may let an attacker with network access run OS commands as root without authenticating. Cisco says the cause is twofold: the use of persistent cookies, and client certificates not being validated even when the cluster TLS verify mode is enabled.

Affected versions. According to Cisco, virtual and appliance versions of Expressway-C and Expressway-E are affected if they run a vulnerable release and are configured in a cluster. Vulnerable releases are X14 and earlier and X15.5.3 and earlier. A standalone, non-clustered X15.5.3 is described as not affected.

Fixed versions and workarounds. X15.5.3 and earlier are fixed in X15.5.20 (NVD also lists releases before X15.5.20 as affected). X14 and earlier must migrate to a fixed release. Cisco's advisory states that there are no workarounds. F6, on the other hand, suggests as a stopgap, if you cannot update, limiting connections to TCP 4371-4372 to trusted cluster nodes only. Note that this is not an official Cisco workaround.

Exploitation. At publication on October 21, Cisco's advisory said it was not aware of public announcements or malicious use. On November 18, F6 then reported an attack on a clustered Expressway (X15.5.3) at an organization in Russia after a public PoC appeared. The attackers reportedly compromised two internet-facing devices, used them to reach two other cluster nodes on the internal network, and gained root access. CISA added the flaw to KEV on November 20. The difference between Cisco's advisory and KEV is probably because the advisory remains at its October 21 version (Final) and does not reflect later exploitation information.

How to check. In the admin interface, check the Expressway version (X14.x or X15.5.x) and whether it is in a cluster. If it is a clustered X15.5.3 or earlier, plan the update to X15.5.20. The fix is also included in the Expressway Series security hardening release Cisco published in October. After updating, ask your vendor to check for suspicious administrator actions and outbound traffic.

Apache Roller CVE-2026-129448 — Pre-authentication deserialization in XML-RPC leads to remote code execution

What happens. Apache Roller is a Java-based blog server. Its XML-RPC endpoint reconstructs (deserializes) extension-type data received from outside before checking that the caller is logged in, so an unauthenticated attacker may be able to run arbitrary code. NVD lists a CVSS v3.1 score of 9.8 (Critical), scored by Apache (security@apache.org).

Affected and fixed versions. CVE-2026-129448 covers Roller 4.0.0 through 6.1.4. Version 6.1.5 is covered by a separate CVE for the same flaw (CVE-2026-82384). Apache recommends upgrading to 6.1.6 or later, which disables the extension types and rejects requests when the XML-RPC feature is disabled.

If you cannot update. Apache advises setting "enabledForExtensions" to "false" in WEB-INF/web.xml, or removing the "/roller-services/xmlrpc" servlet mapping, and restarting Roller. Disabling XML-RPC in the admin UI alone is not enough, because older versions deserialize the request before checking that setting.

Exploitation. Apache's November 17 announcement states that "this issue is being actively exploited," and CISA added it to KEV on November 20 (due November 23). If you run Roller yourself, you also need to check whether you were already compromised (logs, suspicious files, outbound connections), not just update.

SAP NetWeaver Enterprise Portal CVE-2025-42884 — An older flaw added to KEV

What happens. In SAP NetWeaver Enterprise Portal, an unauthenticated attacker can inject JNDI (Java's naming lookup mechanism) environment properties or a URL used in lookups, causing a connection to an unintended provider. This could lead to disclosure or modification of server information; NVD notes there is no impact on availability.

Severity, affected versions and fix. SAP rates it CVSS v3.1 6.5 (Medium). EP-BASIS 7.50 and EP-RUNTIME 7.50 are affected. NVD shows it was published on November 11, 2025, and the fix is covered by SAP Security Note 3660969 (NVD shows that access to it requires permissions). Although it is Medium, CISA confirmed real-world exploitation and added it to KEV on November 20. Even with a low score, a vulnerability confirmed as exploited moves up in priority. If you use SAP NetWeaver, ask your maintenance vendor whether the November 2025 patches have been applied.

VMware vCenter CVE-2026-123890 — Added to KEV (new fact)

The vCenter authentication bypass (CVSS v3.1 9.8) covered in yesterday's article was added to KEV on November 20 (due November 23). Yesterday, we could not find it in the KEV data we could check; this time we confirmed the listing in CISA's catalog. The fixed versions are 9.1.1.0200 / 9.0.2.0200 / 8.0 U3m / VCF 5.2.5, and there is no workaround. Updating does not remove administrator accounts already created or keys already stolen, so you also need to check for compromise. For details, see How to check and respond to the VMware vCenter vulnerability CVE-2026-123890.

Official information: Broadcom VMSA-2026-0009, CISA alert.

Mitel MiCollab CVE-2026-133323 — Unauthenticated command injection in the conferencing component (CVSS 10.0)

What happens. Mitel MiCollab is communications software that combines telephony, conferencing and chat. The Audio, Web and Video Conferencing (AWV) component has insufficient parameter sanitization, so an unauthenticated attacker may be able to carry out blind command injection (running commands without seeing the output). In Mitel's advisory, this item (ID MTLVULN-1864) is CVSS v3.1 10.0 (Critical).

Affected versions and remediation. MiCollab 10.3 (10.3.0.18) and earlier is affected. Mitel provides a patch for 10.3.0.18 (KB000129195), and upgrading to a newer release also resolves it. As a stopgap, the advisory suggests restricting external access to AWV. The same advisory (MISA-2026-0012) covers five issues in total, including MTLVULN-1862 at CVSS 9.0 (Critical), and notes that exploiting them together can amplify the impact. The advisory we checked does not mention exploitation. It was published on November 16 with no CVE assigned yet, but NVD registered CVE-2026-133323 on November 19, and its description names MTLVULN-1864.

JetBrains TeamCity CVE-2026-132891 — Remote code execution via external pull requests

What happens. TeamCity is a server that runs software builds and automated tests (CI/CD). According to the NVD record (JetBrains is the CNA), remote code execution was possible via external pull requests. It is rated CVSS v3.1 9.8 (Critical), scored by JetBrains (cve@jetbrains.com). Affected versions are those before 2026.2, before 2026.1.4 on the 2026.1 line, and before 2025.11.8 on the 2025.11 line. The fixed versions are 2026.2, 2026.1.4 and 2025.11.8. We could not confirm further conditions or workarounds from the sources we could reach, and none mention exploitation. If you run TeamCity yourself, update to the fixed version for your release line.

For non-IT staff: Today's checklist

- Ask your IT contact or vendor whether you use Cisco Expressway (an external connection device for video conferencing). If not, note "not applicable" and stop there
- If you have Expressway, check whether it is clustered and whether it runs X15.5.3 or earlier or X14 or earlier, and ask for an update to X15.5.20 (migration for X14 and earlier). Cisco lists no workaround
- Until the update, ask your vendor whether cluster traffic (TCP 4371-4372) can be limited to trusted devices (a stopgap F6 suggests, not an official Cisco workaround)
- Check whether you run the blog software Apache Roller yourself. If so, update to 6.1.6 or later and ask for a compromise check
- If you use SAP NetWeaver Enterprise Portal, ask your maintenance vendor whether the November 2025 patch (SAP Security Note 3660969) is applied
- If you have VMware vCenter, update to the fixed version and check for compromise, as described in yesterday's article
- If you use Mitel MiCollab, check whether the patch for 10.3.0.18 (KB000129195) is applied and whether AWV is exposed externally
- If you run TeamCity in-house, ask your developers whether it is at 2026.2, 2026.1.4 or 2025.11.8 or later
- The KEV due date is November 23 for all four. If you have an affected product, arrange it today rather than waiting for the new week

Related articles

Detailed vCenter steps are in How to check and respond to the VMware vCenter vulnerability CVE-2026-123890. For yesterday's information, see the November 20 vulnerability digest; for SAP NetWeaver, see also the November 12 vulnerability digest. For preparing against vulnerabilities, see Vulnerability assessment costs and how to choose.

Sources

- Cisco Security Advisory cisco-sa-vcs-static-cred-hr7EWZ8t: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t
- F6 (exploitation of Cisco Expressway CVE-2026-76466, 2026-11-18): https://www.f6.ru/media-center/press-releases/cisco-cve-2026-76466/
- NVD CVE-2026-76466: https://nvd.nist.gov/vuln/detail/CVE-2026-76466
- CISA alert (four added to KEV, 2026-11-20): https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Apache Roller announcement (oss-security, 2026-11-17): https://www.openwall.com/lists/oss-security/2026/11/17/5
- NVD CVE-2026-129448: https://nvd.nist.gov/vuln/detail/CVE-2026-129448
- NVD CVE-2026-82384: https://nvd.nist.gov/vuln/detail/CVE-2026-82384
- NVD CVE-2025-42884: https://nvd.nist.gov/vuln/detail/CVE-2025-42884
- SAP Security Patch Day: https://url.sap/sapsecuritypatchday
- Broadcom VMSA-2026-0009: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- Mitel MISA-2026-0012: https://www.mitel.com/support/security-advisories/mitel-product-security-advisory-misa-2026-0012
- NVD CVE-2026-133323: https://nvd.nist.gov/vuln/detail/CVE-2026-133323
- NVD CVE-2026-132891: https://nvd.nist.gov/vuln/detail/CVE-2026-132891

Frequently asked questions

Is Cisco Expressway unaffected if it is not clustered?

Cisco's advisory says devices are affected if they run a vulnerable release and are configured in a cluster. A standalone, non-clustered X15.5.3 is described as not affected. Still, in case the configuration changes or you cluster later, it is safer to have a plan to update to the fixed version (X15.5.20). X14 and earlier must migrate to a fixed release.

Cisco wrote that it was not aware of exploitation. Why do you call it confirmed exploited?

Cisco's advisory reflects the state at its October 21 publication and says it was not aware of public announcements or malicious use. Later, F6 reported an attack on November 18, and CISA added the flaw to KEV on November 20. In this article, a KEV listing counts as confirmed exploitation. When an advisory and KEV disagree, it is safer to give weight to the newer facts, KEV and the F6 report.

SAP CVE-2025-42884 is only CVSS 6.5. Why the urgency?

CVSS is a theoretical severity based on the nature of the flaw; it does not say whether attacks are happening. CISA lists a flaw in KEV because it confirmed real-world exploitation. Even at Medium, a confirmed-exploited flaw should be handled with higher priority. SAP's fix is covered by Security Note 3660969 from November 2025.

If Mitel MiCollab and TeamCity are not exploited, can they wait?

The sources we checked do not mention exploitation of either. However, they are unauthenticated remote code or command execution flaws rated CVSS 10.0 and 9.8, and attacks become easier once details are public. If they are reachable from outside, consider updating or restricting external exposure this week.

What should I do first if I cannot wait for the vendor's update?

The basic step is to restrict management screens and management traffic to a small set of internal machines. For products where the vendor gives configuration steps, such as Roller, follow them. For products with no workaround in the advisory, such as Cisco's, you can discuss F6's stopgap (limiting TCP 4371-4372) with your vendor, but note that it is not an official workaround.

株式会社オブライト

Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.

Feel free to contact us

Contact Us