Cyber Threat Brief — November 21 2026
1. vCenter Directory Service bypass — CVE-2026-123890
TL;DR: CISA added CVE-2026-123890 on 20 Nov, due 23 Nov, and Mandiant says ARMORY CASTLE used it as a zero-day. Install the VMSA-2026-0009 build for your train, then hunt new SSO admins in vsphere.local.
What’s New:
- CISA lists CVE-2026-123890 as exploited, added 20 Nov, due 23 Nov, with ransomware use Unknown. Broadcom VMSA-2026-0009.1 describes an authentication bypass in the VMware Directory Service, CVSS 9.8, with no workaround, and thanks Mandiant for reporting the issue. The advisory text does not say the bug was exploited. CISA KEV, VMSA-2026-0009.
- The Broadcom matrix lists fixed builds 9.1.1.0200, 9.0.2.0200, and 8.0 U3m, and 5.2.5 for VMware Cloud Foundation 5.x. vCenter 7.0 has no public build. Telco Cloud points at KB463116. The same advisory also lists CVE-2026-123891, CVE-2026-123892, CVE-2026-123893, and CVE-2026-123894. VMSA-2026-0009.
- Mandiant says ARMORY CASTLE, formerly UNC5221, exploited CVE-2026-123890 in early September 2026 with BONESAW at
/tmp/123, then SAWSNAKE at/tmp/sss, to forge SAML sessions. Mandiant says the same intrusion used BeyondTrust Remote Support CVE-2026-102764 before the vCenter bug. Mandiant. - Mandiant says BONESAW reads
/storage/db/vmware-vmdir/data.mdb, writes tenantcredential PEM files, and creates an SSO admin. Mandiant redacts that account assps-<REDACTED>@vsphere.localand says the actor enabled SSH with PUT/rest/appliance/access/ssh. Mandiant.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| VMware vCenter 9.1.1.0200 | Fixed build | T1190 | Config/inventory | Install VMware vCenter 9.1.1.0200 on the 9.1 train and confirm the running build. |
| VMware vCenter 9.0.2.0200 | Fixed build | T1190 | Config/inventory | Install VMware vCenter 9.0.2.0200 on the 9.0 train and confirm the running build. |
| VMware vCenter 8.0 U3m | Fixed build | T1190 | Config/inventory | Install VMware vCenter 8.0 U3m on the 8.0 train and confirm the running build. |
| VMware Cloud Foundation 5.2.5 | Fixed build | T1190 | Config/inventory | Install VMware Cloud Foundation 5.2.5 on the 5.x train and confirm the vCenter build. |
| VMware vCenter 7.0 | No fixed build | T1190 | Config/inventory | Record every VMware vCenter 7.0 appliance. The matrix has no public build for that train. |
| /storage/db/vmware-vmdir/data.mdb | File path | T1005 | EDR file | Search the vCenter appliance for reads or copies of /storage/db/vmware-vmdir/data.mdb. |
| TCP 2012 on vCenter | Network behavior | T1190 | Firewall/NetFlow | Alert on connections to vCenter TCP 2012, the SSO control RPC port BONESAW abuses, from any host that is not a vCenter node. |
| /tmp/123 | File path | T1190 | EDR file | Search internal Linux appliances that can reach vCenter for /tmp/123, the BONESAW path Mandiant names. |
| /tmp/sss | File path | T1606.002 | EDR file | Search those same hosts for /tmp/sss, the SAWSNAKE path Mandiant names. |
| /tmp/dbr | File path | T1571 | EDR file | Search those same hosts for /tmp/dbr, the BEARBONES backdoor Mandiant saw listening on TCP 53 and TCP 33992. |
| /usr/bin/vmtoolscs | File path | T1036.005 | EDR file | Search Linux appliances and vCenter for /usr/bin/vmtoolscs, the LAZYBONES backdoor Mandiant names. |
| ActiveSer.jsp | Webshell | T1505.003 | Web server file | Search web roots, including the Remote Support appliance, for ActiveSer.jsp, the SLIMSAVAGE webshell Mandiant names. |
| SSH-2.0-pulsesecure_23345 | Network banner | T1090 | Network sensor/Zeek | Flag outbound SSH to servers presenting SSH-2.0-pulsesecure_23345 on high ports, which Mandiant ties to the actor’s relay network. |
| idp_key.pem | File name | T1552.004 | EDR file | Search for idp_key.pem and for files whose names contain tenantcredential and end in .key.pem. |
| /rest/appliance/access/ssh | Request path | T1021.004 | vCenter access log | Search vCenter access logs for PUT /rest/appliance/access/ssh. |
| sps- | Account | T1136.002 | vCenter SSO | List new SSO admins in vsphere.local whose names start with sps-. Mandiant redacts the middle of the account. |
| 103.147.251.5 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 103.147.251.5, a suspected obfuscation network IP Mandiant lists. |
| 103.190.38.3 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 103.190.38.3, a suspected obfuscation network IP Mandiant lists. |
| 118.174.128.34 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 118.174.128.34, a suspected obfuscation network IP Mandiant lists. |
| 118.174.128.36 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 118.174.128.36, a suspected obfuscation network IP Mandiant lists. |
| 118.174.128.38 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 118.174.128.38, a suspected obfuscation network IP Mandiant lists. |
| 176.9.89.66 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 176.9.89.66, a suspected obfuscation network IP Mandiant lists. |
| 185.71.15.109 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 185.71.15.109, a suspected obfuscation network IP Mandiant lists. |
| 220.121.128.41 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 220.121.128.41, a suspected obfuscation network IP Mandiant lists. |
| 222.108.77.44 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 222.108.77.44, a suspected obfuscation network IP Mandiant lists. |
| 61.216.56.127 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 61.216.56.127, a suspected obfuscation network IP Mandiant lists. |
| 81.45.89.43 | IOC | T1090 | Firewall/proxy | Block and search firewall and proxy logs for 81.45.89.43, a suspected obfuscation network IP Mandiant lists. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | None — verified | Nearest search is an SSH banner allowlist, not vmdir or SSO admin logic. |
| Elastic | None — verified | vpxuser SSH rule misses root SSH and the VAMI enable call. |
| Sigma | None — verified | SAML rules target cloud IdPs, not vCenter STS. |
Hunt hint: Install the fixed build for the train you run, and keep vCenter 7.0 on a separate list because the matrix has no public build. In SSO logs, list new administrator accounts in vsphere.local, including any name that starts with sps-. Search the appliance for reads of /storage/db/vmware-vmdir/data.mdb and for tenantcredential PEM files or idp_key.pem. Search access logs for PUT /rest/appliance/access/ssh. Alert on TCP 2012 connections to vCenter from non-vCenter hosts, and on internal Linux appliances look for /tmp/123, /tmp/sss and /tmp/dbr; Mandiant’s post also ships YARA rules for SLIMSAVAGE, CAGEMATCH and SAWSNAKE. If a signing key was copied, rotate the STS certificate, because forged SAML sessions (T1606.002) survive the patch.
Sources: CISA KEV, VMSA-2026-0009, Mandiant.
2. Apache Roller XML-RPC — CVE-2026-129448
TL;DR: CISA added CVE-2026-129448 on 20 Nov, due 23 Nov, and Apache says the XML-RPC bug is being exploited. Upgrade to Apache Roller 6.1.6 or later, or set enabledForExtensions to false and restart.
What’s New:
- CISA lists CVE-2026-129448 as exploited, added 20 Nov, due 23 Nov, with ransomware use Unknown. Apache’s 17 Nov mail says versions 4.0.0 through 6.1.4 deserialize vendor extension types on the XML-RPC endpoint before authentication, and says this is the same bug as CVE-2026-82384. Apache says the issue is being actively exploited. CISA KEV, Apache 17 Nov.
- Apache’s September mail says CVE-2026-82384 affects 6.1.5 only. Both mails say to upgrade to 6.1.6 or later, which disables extension types and rejects XML-RPC when the feature is off. Apache 25 Sep, Roller security.
- Apache says set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart. Apache says turning XML-RPC off in the administration UI is not enough on older versions, because parsing happens before that check. Apache 17 Nov.
- The public README by Yanis Alim says a POST to /roller-services/xmlrpc, or /roller/roller-services/xmlrpc, reaches the parser, and says 6.1.5 still ships enabledForExtensions true. This brief did not run that repository. README.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| Apache Roller 6.1.6 | Fixed build | T1190 | Config/inventory | Install Apache Roller 6.1.6 or a later 6.1 release and restart the JVM. |
| enabledForExtensions | Config | T1190 | File integrity | Set enabledForExtensions to false in WEB-INF/web.xml and restart Roller. |
| /roller-services/xmlrpc | Request path | T1190 | Web/proxy access | Search access logs for POST /roller-services/xmlrpc. |
| /roller/roller-services/xmlrpc | Request path | T1190 | Web/proxy access | Search access logs for POST /roller/roller-services/xmlrpc. |
| lab.ProbeGhost | Response string | T1190 | Web/proxy access | Search response bodies for Failed to load class for result object: lab.ProbeGhost. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | None — verified | No search matches POST /roller-services/xmlrpc. |
| Elastic | Partial — Potential Java Service Exploitation via Suspicious Child Process | Needs a shell or curl child within 5s of the accept. |
| Sigma | Partial — Suspicious Java Children Processes | Needs a shell, curl, or python child of java. |
Hunt hint: Upgrade to Apache Roller 6.1.6 or later and restart the JVM. Search access logs for POST /roller-services/xmlrpc and for POST /roller/roller-services/xmlrpc. Open WEB-INF/web.xml and confirm enabledForExtensions is false. A response body containing lab.ProbeGhost means the public detector reached the parser. Turning XML-RPC off in the admin UI does not stop parsing on the versions Apache names. After the change, a request that uses the extension tag should be rejected.
Sources: CISA KEV, Apache 17 Nov, Apache 25 Sep, Roller security, README.
3. LiteLLM guardrail sandbox — CVE-2026-40217
TL;DR: CISA added CVE-2026-40217 on 18 Nov, due 2 Dec. Upgrade LiteLLM to 1.83.11 or later, and block POST /guardrails/test_custom_code until that build is running.
What’s New:
- CISA lists CVE-2026-40217 as exploited, added 18 Nov, due 2 Dec, with ransomware use Unknown. The entry names code execution by bytecode rewriting at /guardrails/test_custom_code. CISA KEV.
- The GitHub advisory says affected versions are 1.81.8 up to but not including 1.83.10. The patched-versions header says 1.83.10 or later. The body says fixed in 1.83.11 and says to upgrade to 1.83.11 or later. The references line names v1.83.10-stable. Follow the body and install 1.83.11 or later. GHSA-wxxx-gvqv-xp7p.
- The advisory says reaching the endpoint requires a proxy-admin credential in default configurations. It also says the proxy process runs as root in the default Docker image. GHSA-wxxx-gvqv-xp7p.
- The advisory says to block POST /guardrails/test_custom_code at the reverse proxy or API gateway when an upgrade is not immediate. GHSA-wxxx-gvqv-xp7p.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| LiteLLM 1.83.11 | Fixed build | T1190 | Config/inventory | Install LiteLLM 1.83.11 or a later 1.83 build and restart the proxy. |
| /guardrails/test_custom_code | Request path | T1190 | Reverse proxy | Block POST /guardrails/test_custom_code, and search logs for that path. |
| litellm 1.81.8 | Affected range | T1190 | Config/inventory | Find litellm packages from 1.81.8 up to but not including 1.83.11 and queue them for the fixed build. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | None — verified | PTH-file rule is a package install, not the guardrail POST. |
| Elastic | None — verified | Matches a package stealer plus IMDS, not this POST. |
| Sigma | None — verified | No rule names POST /guardrails/test_custom_code. |
Hunt hint: Upgrade the proxy to LiteLLM 1.83.11 or later and restart it. Until that build is running, block POST /guardrails/test_custom_code at the reverse proxy. Search proxy logs for that path and keep any hit that presented a proxy-admin key. The default image runs the process as root, so list unexpected child processes after a hit. Do not treat 1.83.10 as the finish line, because the advisory body says 1.83.11.
Sources: CISA KEV, GHSA-wxxx-gvqv-xp7p.
Detection index: ESCU 21509485465a (2026-11-21) · elastic detection-rules 9d792a8f6731 (2026-11-20) · SigmaHQ 698f0912f571 (2026-11-18).
Status Updates
- SonicWall SonicOS (CVE-2026-19868): SonicWall-SonicOS-CVE-2026-19868 is now overdue. The KEV date was 20 Nov. The fix remains 7.3.4-7013 and 8.2.3-8015. SNWLID-2026-0014, 19 Nov brief.
- Apache Axis (CVE-2026-90436): Apache-Axis-CVE-2026-90436-2026-11 is due today, 21 Nov. Confluence Data Center 9.2.28 remains the fixed build Atlassian lists. 19 Nov brief.
- REDCap (CVE-2026-90817): REDCap-CVE-2026-90817-2026-11 is due today, 21 Nov. No projectredcap.org build was named on 19 Nov, and that is unchanged. 19 Nov brief.
- Synology DSM (CVE-2024-10441): Synology-DSM-CVE-2024-10441-2026-11 is due today, 21 Nov. The SA-24:20 builds remain those in the 19 Nov brief. SA-24:20, 19 Nov brief.
- Apple (CVE-2024-27834): Apple-CVE-2024-27834-2026-11 remains overdue. The KEV date was 18 Nov. No new build. 19 Nov brief.
- Check Point Gaia (CVE-2026-123039): CheckPoint-Gaia-CVE-2026-123039-2026-11 remains overdue. The KEV date was 16 Nov. No new material. 13 Nov brief.
- UnrealIRCd (CVE-2026-114713): UnrealIRCd-CVE-2026-114713-2026-11 remains overdue. The KEV date was 16 Nov. The fix remains 6.2.7.1. Forum, 19 Nov brief.
- Openwave Webtop (CVE-2026-111793): Openwave-Webtop-CVE-2026-111793 was added to KEV on 2026-11-10 and is not yet briefed. Due 24 Nov. The vendor fix remains 1.1.22.0. Advisory, 17 Nov brief.
- Cisco Expressway (CVE-2026-76466): Cisco-Expressway-CVE-2026-76466-2026-11. KEV added 2026-11-20, not yet briefed. Due 23 Nov. Cisco lists first fixed release X15.5.20. Cisco.
- SAP NetWeaver (CVE-2025-42884): SAP-NetWeaver-CVE-2025-42884-2026-11. KEV added 2026-11-20, not yet briefed. Due 23 Nov. Note 3660969 is on a login wall. Not the deferred ICM2SHELL item.
- Retired from watch: Barracuda-ESG-CVE-2026-116606-2026-11 (Barracuda ESG). KEV due 13 Nov has passed with no material change since 11 Nov. 17 Nov brief.
- Watching (no change): ARTEX-Software-Vendors-2026-11; Barracuda-Cloud-ARTEX-Intrusion-2026-11; Binance-TraderTraitor-2026-11; Chrome-CVE-2026-125350-2026-11; Cisco-BroadWorks-CVE-2026-20320; Copeland-XWEB-EVO-2026-11; Cursor-Fireworks-Key-Compromise-2026-11; GitHub-wfx-loot-CI-stealer-2026-11; LNbits-server-shutdown-2026-11; Microsoft-Outlook-CVE-2026-124194; Microsoft-agent-framework-PyPI-2026-11; N-able-NCentral-Able2Shell-2026-11; OpenJDK-Java4Shell-CVE-2026-114938-2026-11; Optimizely-OPTIMJACK-Supply-Chain-2026-11; Puppet-Enterprise-CVE-2026-115731-2026-11; Refrigeration-Controllers-EU-2026-11; ScreenConnect-CryptoBait-Sessions-2026-11; ScreenConnect-SCKit-RMMplus-2026-11; Windows-SignDrop-LPE-2026-11; eMudhra-CVE-2026-111943 (19 Nov brief).