On November 20, 2026, CISA added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog based on evidence of active exploitation in the wild. This is not a theoretical exercise — every entry in the KEV represents a flaw that adversaries are using against real organizations right now. The four additions span enterprise collaboration, virtualization management, application servers, and network edge infrastructure:
- CVE-2025-42884 — SAP NetWeaver: Improper Neutralization of Special Elements in Data Query Logic (code/query injection class)
- CVE-2026-76466 — Cisco Expressway Series: Use of Hard-coded Credentials
- CVE-2026-123890 — VMware vCenter: Authentication Bypass Using an Alternate Path or Channel
- CVE-2026-129448 — Apache Roller: Deserialization of Untrusted Data
Under Binding Operational Directive (BOD) 26-04, Prioritizing Security Updates Based on Risk, federal civilian executive branch agencies are required to remediate KEV-listed vulnerabilities within mandated timelines. But the KEV is not just a federal compliance artifact — it is the single highest-signal prioritization feed available to any vulnerability management program. If your organization runs any of these products, these four CVEs move to the front of your patch queue today.
Technical Analysis
CVE-2025-42884 — SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic
This is an injection-class vulnerability in SAP NetWeaver, the application server platform underpinning a large percentage of the world's SAP ERP, S/4HANA, and business suite deployments. Improper neutralization of special elements in data query logic means attacker-controlled input reaches a query construction layer without adequate sanitization, allowing manipulation of the underlying query structure.
From a defender's perspective, the exploitation chain typically looks like this:
- An unauthenticated or low-privileged remote attacker submits crafted input to an exposed NetWeaver web service or application endpoint (commonly over HTTP/HTTPS on ports 50000, 8000, or 44300-series depending on instance numbering).
- Special elements in the input are not neutralized before being incorporated into data query logic.
- The attacker reads, modifies, or exfiltrates backend data — in an SAP context, that frequently means financial records, HR data, or credential material that enables further privilege escalation within the landscape.
SAP systems hold the crown jewels of most enterprises that run them. An injection flaw with confirmed active exploitation should be treated as a potential precursor to business data theft, fraud (e.g., payment redirection), and lateral movement — SAP hosts are routinely among the least-monitored Tier 0 assets in the environment.
CVE-2026-76466 — Cisco Expressway Series Use of Hard-coded Credentials
Hard-coded credentials in a network edge device is about as severe as infrastructure vulnerabilities get. Cisco Expressway (Expressway-C and Expressway-E) provides firewall traversal and remote access for Cisco collaboration deployments — meaning Expressway-E sits on the network perimeter by design, internet-facing, handling inbound signaling for video and voice collaboration.
A hard-coded credential flaw means an embedded account exists with a fixed username/password that cannot be changed or removed through normal administrative interfaces. The exploitation requirements are trivially low:
- Attacker identifies an exposed Expressway management or service interface.
- Attacker authenticates using the known hard-coded credential (obtainable from firmware analysis or public disclosure).
- Depending on the account's privilege level, the attacker gains administrative control of the edge node — a foothold on the perimeter with visibility into collaboration traffic and a pivot point into the internal network.
Treat any internet-facing Expressway node as potentially compromised if it was exposed and unpatched during the exploitation window. Password rotation alone does not remediate a hard-coded credential — only the vendor fix does.
CVE-2026-123890 — VMware vCenter Authentication Bypass Using an Alternate Path or Channel
vCenter is the management plane for the entire virtualized estate. An authentication bypass via an alternate path or channel means there exists an access route — an API endpoint, service port, or internal handler — that reaches authenticated functionality without passing through the normal authentication controls.
The implications are severe: an attacker who bypasses vCenter authentication can enumerate and control every ESXi host and VM under management. In the ransomware playbook, vCenter compromise is the force multiplier — it enables mass VM encryption, snapshot deletion, and datastore destruction in a single operation. This is precisely the pattern we have seen in ransomware engagements over the past several years: gain vCenter access, deploy encryption at the hypervisor layer, delete backups, maximize impact.
Exploitation requirements: network reachability to the vulnerable vCenter service. vCenter should never be internet-exposed — if yours is, that is an architectural failure to correct immediately regardless of patch status.
CVE-2026-129448 — Apache Roller Deserialization of Untrusted Data
Apache Roller is an open-source, Java-based blog server. Java deserialization vulnerabilities are a well-understood remote code execution primitive: the application accepts serialized Java objects from an untrusted source and deserializes them without validation, allowing an attacker to supply a malicious object graph whose deserialization triggers arbitrary code execution (classic gadget-chain exploitation).
The attack chain:
- Attacker identifies a Roller endpoint that accepts serialized objects.
- Attacker crafts a malicious serialized payload using gadget classes present in the application classpath (commons-collections and similar libraries are the usual suspects).
- Deserialization executes the payload with the privileges of the Roller application server process — typically leading to webshell deployment or reverse shell establishment.
Post-exploitation on the Java application server host usually follows quickly: webshells dropped into the web root, outbound C2 connections from the Java process, and lateral movement attempts from the compromised host.
Exploitation Status
All four CVEs are confirmed actively exploited — that is the inclusion criterion for the CISA KEV Catalog. Federal agencies are bound by BOD 26-04 remediation timelines; private-sector organizations should treat the CISA-published due date as their own deadline, not a suggestion.
Detection & Response
The detections below target the most reliable post-exploitation observables for these flaws: anomalous child processes from SAP, Java, and web server services; hard-coded credential usage against Cisco edge infrastructure; and unauthenticated access patterns against vCenter management interfaces. Tune thresholds to your baseline — an SAP dispatcher or Tomcat JVM spawning a shell is essentially never legitimate.
Sigma Rules
---
title: SAP NetWeaver Process Spawning Shell or Script Interpreter
tid: 3f8a1c42-7b2e-4d91-a6c3-9e5f2d8b1a47
status: experimental
description: Detects SAP NetWeaver dispatcher or server processes spawning command shells or script interpreters, consistent with post-exploitation activity following injection attacks such as CVE-2025-42884.
references:
- https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/11/20
tags:
- attack.execution
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\disp+work.exe'
- '\jstart.exe'
- '\igswd.exe'
- '\sapstartsrv.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
condition: selection_parent and selection_child
falsepositives:
- Rare SAP administrative maintenance scripts - verify against change windows
level: high
---
title: Java Application Server Spawning Shell - Apache Roller Deserialization
tid: 8c2d5e91-4a6b-4f38-b9d2-1e7a3c5f8d62
status: experimental
description: Detects Java/Tomcat application server processes spawning shells or download tools, consistent with post-exploitation of Java deserialization flaws such as CVE-2026-129448 in Apache Roller.
references:
- https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- https://attack.mitre.org/techniques/T1090/
author: Security Arsenal
date: 2026/11/20
tags:
- attack.execution
- attack.t1059
- attack.initial_access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\java.exe'
- '\javaw.exe'
- '\tomcat.exe'
- '\catalina.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
- '\wget.exe'
condition: selection_parent and selection_child
falsepositives:
- Application deployment pipelines invoking scripts from JVM - baseline and exclude known CI/CD service accounts
level: high
---
title: Webshell File Creation in Java Web Application Directory
tid: 5b1f8d34-9c2a-4e67-a3b8-6d4f1c9e2a75
status: experimental
description: Detects creation of script files in web-accessible application directories by the web server process account, consistent with webshell deployment after exploitation of flaws such as CVE-2026-129448.
references:
- https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- https://attack.mitre.org/techniques/T1505/003/
author: Security Arsenal
date: 2026/11/20
tags:
- attack.persistence
- attack.t1505.003
logsource:
category: file_event
product: windows
detection:
selection_path:
TargetFilename|contains:
- '\webapps\'
- '\roller\'
- '\htdocs\'
- '\wwwroot\'
selection_ext:
TargetFilename|endswith:
- '.jsp'
- '.jspx'
- '.war'
- '.aspx'
- '.php'
filter_deploy:
Image|endswith:
- '\msiexec.exe'
- '\wusa.exe'
condition: selection_path and selection_ext and not filter_deploy
falsepositives:
- Legitimate application deployments - correlate with change management records
level: medium
KQL — Microsoft Sentinel / Defender
The following queries hunt for (1) suspicious child processes from SAP, Java, and web server processes across Windows and Linux endpoints, and (2) unauthenticated/anomalous access to vCenter and Cisco Expressway management interfaces via network logs.
// Hunt 1: SAP, Java/Tomcat, or web server processes spawning shells (post-exploitation)
// Covers CVE-2025-42884 (SAP NetWeaver) and CVE-2026-129448 (Apache Roller) post-exploitation behavior
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName has_any ("disp+work", "jstart", "sapstartsrv", "java", "javaw", "tomcat", "catalina", "httpd", "nginx")
| where FileName has_any ("cmd.exe", "powershell.exe", "pwsh.exe", "sh", "bash", "dash", "certutil.exe", "curl", "wget", "nc", "ncat")
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName, InitiatingProcessRemoteIP
| order by TimeGenerated desc
;
// Hunt 2: Network connections to vCenter (443/9443) and Cisco Expressway management from unusual sources
// Relevant to CVE-2026-123890 (vCenter auth bypass) and CVE-2026-76466 (Expressway hard-coded creds)
// Requires CommonSecurityLog ingestion (firewall/CEF) - adjust device vendor filter to your perimeter gear
CommonSecurityLog
| where TimeGenerated > ago(14d)
| where DestinationPort in (443, 9443, 2222, 8443)
| where DeviceAction !in ("Deny", "Drop", "Blocked")
| summarize ConnectionCount = count(), DistinctSources = dcount(SourceIP), Sources = make_set(SourceIP, 25)
by DestinationIP, DestinationPort, DeviceProduct
| where DistinctSources > 10 or ConnectionCount > 500
| order by ConnectionCount desc
;
// Hunt 3: Authentication anomalies against vCenter via Syslog (successful logins from non-jump-host sources)
Syslog
| where TimeGenerated > ago(14d)
| where SyslogMessage has_any ("vpxd", "vCenter", "sso") and SyslogMessage has "logged in"
| extend SourceHost = extract(@"from ([0-9.]+)", 1, SyslogMessage)
| summarize LoginCount = count(), Events = make_set(SyslogMessage, 10) by Computer, SourceHost, bin(TimeGenerated, 1h)
| order by LoginCount desc
Velociraptor VQL
Use this hunt artifact on Linux hosts running Apache Roller or SAP NetWeaver to identify suspicious child processes of the Java/SAP services and recent webshell-style file drops in web application directories.
-- Hunt: Suspicious child processes of Java/SAP services and recent web-root file drops
-- Relevant to CVE-2026-129448 (Apache Roller deserialization) and CVE-2025-42884 (SAP NetWeaver)
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(cmd|powershell|/bin/sh|/bin/bash|curl |wget |nc |ncat |base64)'
AND (
Name =~ '(java|tomcat|catalina|disp\\+work|jstart|sapstartsrv)'
OR Exe =~ '(java|tomcat|catalina|sap)'
)
-- Hunt: Recently created script files in web application directories (webshell triage)
SELECT FullPath, Size, Mtime, Ctime
FROM glob(globs=['/var/lib/tomcat*/webapps/**/*.jsp', '/opt/roller/**/*.jsp', '/var/www/**/*.jsp', '/var/www/**/*.php'])
WHERE Mtime > now() - 1209600
ORDER BY Mtime DESC
Remediation / Verification Script
Use the following Bash script on Linux application hosts to inventory exposure and gather quick triage artifacts for the SAP, Apache Roller, and vCenter-adjacent components. Run the PowerShell block on Windows vCenter Server instances to confirm patching posture and review recent logins.
#!/bin/bash
# KEV triage script - CVE-2025-42884, CVE-2026-129448, CVE-2026-76466, CVE-2026-123890
# Run as root on Linux app/middleware hosts
echo "=== [1] Listening services on common SAP/Tomcat/management ports ==="
ss -tlnp | grep -E ':(50000|50013|8000|8005|8080|8443|44300|9443)' || echo "None found"
echo "=== [2] Apache Roller deployment check ==="
find / -iname "roller*.war" -o -iname "roller*.jar" 2>/dev/null | head -20
find /opt /usr/share /var/lib -maxdepth 4 -iname "*roller*" -type d 2>/dev/null | head -10
echo "=== [3] Tomcat/Java versions (patch baseline for deserialization fix) ==="
for d in /opt/tomcat* /usr/share/tomcat* /var/lib/tomcat*; do
[ -d "$d" ] && cat "$d/RELEASE-NOTES" 2>/dev/null | head -3
done
java -version 2>&1 | head -2
echo "=== [4] Recent JSP/webshell-style files in web roots (last 14 days) ==="
find /var/lib/tomcat*/webapps /opt/roller /var/www -name "*.jsp" -mtime -14 2>/dev/null | head -30
echo "=== [5] Suspicious child processes of java/tomcat (current) ==="
ps auxf | grep -E 'java|tomcat' | grep -E 'sh |bash |curl |wget |nc ' | grep -v grep || echo "None found"
echo "=== [6] Outbound connections from java processes ==="
ss -tnp 2>/dev/null | grep -i java | grep -v ':8080\|:8443' | head -20 || echo "None found"
# vCenter (Windows-based) verification - CVE-2026-123890
# 1) Confirm vCenter build against the patched build in VMware's advisory
$vc = Get-WmiObject -Class Win32_Product -ErrorAction SilentlyContinue | Where-Object { $_.Name -like "*vCenter*" }
$vc | Select-Object Name, Version, InstallDate
# 2) Review recent successful logons on the vCenter host for anomalies
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624; StartTime=(Get-Date).AddDays(-7)} -MaxEvents 500 |
Where-Object { $_.Message -notmatch 'SYSTEM|NETWORK SERVICE|LOCAL SERVICE' } |
Select-Object TimeCreated, @{N='Account';E={($_.Properties[5]).Value}}, @{N='SourceIP';E={($_.Properties[18]).Value}} |
Sort-Object TimeCreated -Descending | Format-Table -AutoSize
# 3) Verify vCenter is NOT internet-exposed - check perimeter bindings and listening services
Get-NetTCPConnection -State Listen | Where-Object { $_.LocalPort -in 443,9443,5480 } |
Select-Object LocalAddress, LocalPort, OwningProcess |
ForEach-Object { $_ | Add-Member -NotePropertyName Process -NotePropertyValue (Get-Process -Id $_.OwningProcess).ProcessName -PassThru } |
Format-Table -AutoSize
# 4) Confirm no unexpected local admin accounts (post-exploitation persistence check)
Get-LocalGroupMember -Group "Administrators" | Select-Object Name, ObjectClass, PrincipalSource
Remediation
Apply the following steps immediately, in priority order. Confirm exact fixed versions against the vendor advisories — patch build numbers vary by product train.
1. Patch all four products against the vendor-fixed releases.
- SAP NetWeaver (CVE-2025-42884): Apply the SAP Security Note addressing this CVE from SAP's Security Patch Day release. Verify the note is implemented via transaction
SNOTE(for ABAP) or the relevant SUM/SPAM update path, and confirm kernel/IIS-compatible components are updated per the note's prerequisites. Advisory: https://me.sap.com/notes and https://support.sap.com/en/my-support/knowledge-base/security-notes-news.html - Cisco Expressway (CVE-2026-76466): Upgrade Expressway-C and Expressway-E to the fixed release listed in Cisco's security advisory. There is no workaround for hard-coded credentials — configuration changes do not remove the embedded account. Advisory: https://sec.cloudapps.cisco.com/security/center/publicationListing.x
- VMware vCenter (CVE-2026-123890): Update vCenter Server to the patched build per Broadcom/VMware's VMSA advisory. For VCSA, apply via the Appliance Management Interface (port 5480) or
software-packagesCLI. Advisory: https://support.broadcom.com/web/ecx/security-advisory - Apache Roller (CVE-2026-129448): Upgrade to the fixed Roller release from the Apache project. If immediate upgrade is not possible, restrict network access to the Roller administrative and API endpoints and review the classpath for known gadget-chain libraries. Advisory: https://roller.apache.org/ and https://www.cve.org/CVERecord?id=CVE-2026-129448
2. Meet the CISA KEV remediation deadline. Check the KEV Catalog entry for the BOD 26-04 due date assigned to each CVE. Federal agencies must comply; all other organizations should adopt the same date as an internal SLA. Catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
3. Assume breach on internet-facing, unpatched systems. For any Expressway node, vCenter instance, Roller server, or SAP service that was internet-reachable and unpatched during the exploitation window: collect forensic images before patching where feasible, review authentication and access logs for the exposure period, hunt with the detections above, and rotate all credentials that transited or resided on the device.
4. Eliminate management-plane exposure. vCenter (ports 443, 5480, 9443), Expressway management interfaces, and SAP management services must not be reachable from the internet. Restrict to dedicated management VLANs and jump hosts with MFA. Validate with an external attack surface scan — don't trust your firewall spreadsheet.
5. Harden post-patch. Enforce MFA/SSO on vCenter, disable unused SAP ICF services (SICF), restrict Roller registration and API endpoints, and ensure EDR coverage on SAP and application server hosts — these systems are chronically under-monitored.
6. Verify detection coverage. Deploy the Sigma rules and Sentinel queries above, and confirm you are ingesting Syslog from vCenter/ESXi, NetFlow or firewall logs for Expressway nodes, and endpoint telemetry from SAP and Tomcat hosts.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.