
CISA’s Known Exploited Vulnerabilities (KEV) Catalog continues to highlight security weaknesses that have moved beyond theoretical risk into known exploitation.
Between 17 and 20 November 2026, nine vulnerabilities were reported as added to the catalog, affecting Perforce Puppet Enterprise, Synology DSM, BerriAI LiteLLM, Apache Axis, Vanderbilt REDCap, SAP NetWeaver, VMware vCenter, Apache Roller and Cisco Expressway.
What makes this week’s additions interesting is the diversity of affected technologies. Alongside traditional enterprise applications, the list includes AI infrastructure, virtualization management platforms, research-data systems and legacy application frameworks.
Here is a closer look at the vulnerabilities and their security implications.
1. Perforce Puppet Enterprise: Deserialization of Untrusted Data
CVE-2026-115731 | Added: 17 November 2026 | CVSS 9.4
Puppet Enterprise is used to automate infrastructure configuration and manage systems across enterprise environments.
This vulnerability involves the deserialization of untrusted data. When an application processes attacker-controlled serialized objects without adequate validation, it can potentially execute unintended operations, including arbitrary code execution.
The concern is particularly relevant because configuration-management platforms often operate with elevated privileges and have access to multiple systems across an enterprise.
Organizations using Puppet Enterprise should identify affected releases, apply Perforce’s recommended security updates and review the security of their management infrastructure.
2. Synology DSM: Improper Output Encoding
CVE-2024-10441 | Added: 18 November 2026 | CVSS 9.8
Synology DiskStation Manager (DSM) is affected by an improper output-encoding vulnerability involving its system plugin daemon.
The issue can allow a remote attacker to execute arbitrary code on vulnerable systems.
Network-attached storage platforms frequently hold business documents, backups and other sensitive information. A compromise can therefore create consequences beyond the storage appliance itself.
Organizations using affected Synology devices should review the vendor’s security advisory, update vulnerable DSM releases and investigate suspicious access or activity.
3. BerriAI LiteLLM: Unprotected Alternate Channel
CVE-2026-40217 | Added: 18 November 2026 | CVSS 8.8
One of the more interesting additions this week affects LiteLLM, a platform used to connect applications with different large language models.
The vulnerability involves the /guardrails/test_custom_code endpoint. Specially crafted Python bytecode can bypass the intended restrictions and allow arbitrary code execution through this functionality.
CISA classifies the issue as an unprotected alternate channel vulnerability.
This deserves attention because AI gateways are increasingly becoming part of enterprise application architecture. They connect to internal APIs, model providers, data sources and other business services.
Organizations deploying LiteLLM should identify affected versions, apply the vendor’s security updates and review access to custom-code testing functionality.
AI infrastructure should no longer sit outside conventional vulnerability management and security monitoring programmes.
4. Apache Axis: Unsafe Reflection
CVE-2026-90436 | Added: 18 November 2026 | CVSS 9.8
Apache Axis 1.x is affected by an unsafe reflection vulnerability involving the deserialization of inbound SOAP fault messages.
The issue occurs when specially crafted SOAP fault information causes the application to load and instantiate a class identified in the exception details. Under suitable conditions, this can lead to arbitrary code execution.
The concerning part is that this processing occurs before the application’s normal service-level handler chain. Consequently, authentication handlers configured at the service level may not protect against the vulnerable processing path.
Apache Axis 1.x is end-of-life, and organizations still depending on this framework should consider migrating to a supported alternative such as Apache Axis2.
Where migration cannot happen immediately, evaluate available mitigation guidance and restrict exposure of vulnerable services.
Legacy application frameworks remain a security concern when they continue supporting business-critical services without active maintenance.
5. Vanderbilt REDCap: Code Injection
CVE-2026-90817 | Added: 18 November 2026 | CVSS 9.8
Vanderbilt REDCap contains a code-injection vulnerability affecting survey passthrough routing and data-import processing.
A specially crafted HTTP request can reach an unintended controller route from a public survey context and supply manipulated file-path or stream parameters during data import.
The vulnerability can allow an unauthenticated attacker to execute arbitrary code on the server. Exploitation requires knowledge of a valid public survey hash.
REDCap is used for research-data collection and survey management. An exposed installation can therefore create both application-security and data-protection concerns.
Organizations should identify affected deployments, review public survey exposure and apply the vendor’s remediation guidance.
6. SAP NetWeaver: JNDI-Related Security Vulnerability
CVE-2025-42884 | Added: 20 November 2026 | CVSS 6.5
SAP NetWeaver Enterprise Portal is affected by an improper neutralization vulnerability involving special elements in data-query logic.
The issue concerns the handling of JNDI-related environment properties and URL values during lookup operations. Under vulnerable conditions, an unauthenticated attacker can manipulate these values and potentially disclose or modify server information.
SAP NetWeaver continues to support important enterprise business processes, making vulnerabilities in this environment relevant to organizations operating business-critical SAP infrastructure.
Administrators should review SAP Security Note 3660969, establish whether their installations are affected and implement the prescribed security updates.
This is another example of why vulnerability prioritization should not rely entirely on CVSS scores. KEV inclusion provides an additional signal that the issue deserves attention.
7. VMware vCenter: Authentication Bypass
CVE-2026-123890 | Added: 20 November 2026 | CVSS 9.8
One of this week’s most significant additions affects Broadcom VMware vCenter.
The vulnerability involves authentication bypass using an alternate path or channel in vCenter. An attacker with network access to an affected system could potentially bypass normal authentication controls and obtain unauthorized access.
The consequences can be significant because vCenter provides centralized management of virtualized infrastructure, including hosts, virtual machines and associated resources.
A compromise of the management platform can therefore extend across an organization’s virtual environment rather than remaining confined to one application.
Organizations should prioritize affected vCenter deployments, apply the updates specified in Broadcom’s VMSA-2026-0009 advisory and investigate suspicious authentication or administrative activity.
Previously exposed systems should also be assessed for possible compromise. Applying a patch does not establish that an attacker has not already accessed the environment.
8. Apache Roller: Deserialization of Untrusted Data
CVE-2026-129448 | Added: 20 November 2026 | CVSS 9.8
Apache Roller is affected by an unauthenticated deserialization vulnerability in its XML-RPC endpoint.
The vulnerable endpoint processes certain vendor extension types before authenticating the requester. An attacker may exploit this behaviour to trigger unsafe object deserialization and potentially execute arbitrary code.
Apache Roller versions 4.0.0 through 6.1.4 are affected. Version 6.1.6 or later is identified as the recommended upgrade.
Organizations should prioritize upgrading affected deployments. Where immediate upgrading is not possible, follow Apache’s mitigation guidance, including disabling vulnerable extension functionality or removing the XML-RPC servlet mapping as applicable.
The important distinction is that disabling XML-RPC through the administration interface alone is not sufficient for affected older releases.
9. Cisco Expressway: Use of Hard-Coded Credentials
CVE-2026-76466 | Added: 20 November 2026 | CVSS 9.8
Cisco Expressway Series is affected by a critical vulnerability involving hard-coded credentials in its database service functionality.
The vulnerability can potentially allow an attacker to access the database service using the affected credentials and invoke RPC commands capable of executing operating-system commands with root privileges.
Cisco’s advisory describes additional conditions involving persistent cookies and client-certificate validation in particular clustering configurations.
Since Expressway supports enterprise collaboration and communication infrastructure, compromise could affect services beyond the appliance itself.
Organizations should review Cisco’s security advisory, identify affected deployments and apply the prescribed software updates. Access to the database service and relevant authentication material should also be reviewed.
What Security Teams Should Prioritize
This week’s additions cover several important technology layers. Rather than treating them as isolated patching tasks, security teams should assess the wider infrastructure implications.
The immediate priorities should include:
- Virtualization: Validate VMware vCenter exposure and investigate potential authentication bypass attempts.
- Network infrastructure: Review Cisco Expressway deployments and apply the recommended updates.
- AI infrastructure: Include LiteLLM and other AI orchestration components in software inventories and vulnerability assessments.
- Application infrastructure: Identify exposed Apache Axis, Apache Roller and REDCap deployments.
- Enterprise platforms: Review SAP NetWeaver, Puppet Enterprise and Synology deployments for affected versions.
- Verification: Rescan affected systems and confirm that remediation has been completed successfully.
For systems that were exposed before patching, security teams should also investigate whether exploitation occurred and whether additional containment or credential rotation is necessary.


