Executive Summary

In November 2026, CISA added four critical vulnerabilities—CVE-2026-90436 (Apache Axis RCE), CVE-2026-90817 (REDCap code injection), CVE-2026-40217 (LiteLLM privilege escalation), and CVE-2024-10441 (Synology DSM RCE)—to its Known Exploited Vulnerabilities catalog following confirmed active exploitation. Threat actors weaponized CVE-2026-90436 against Atlassian Confluence instances to harvest credentials, query cloud data warehouses, and perform AS-REP Roasting within minutes of initial access. CVE-2026-90817 enabled cryptominer deployment via in-memory loaders, CVE-2026-40217 was leveraged in LLMjacking campaigns targeting financial and retail sectors, and CVE-2024-10441 facilitated C3RB3R ransomware deployment against Synology NAS devices.

These four KEV additions represent a convergence of ransomware, cryptomining, and AI infrastructure abuse into a single advisory cycle, signaling that attackers are simultaneously targeting legacy SOAP libraries, research data platforms, AI inference APIs, and storage appliances—broadening the attack surface enterprises must defend in real time.

Why This Matters Now

CISA's November 2026 KEV additions span four distinct threat categories—ransomware, cryptomining, LLMjacking, and credential theft—exploited concurrently across unpatched and end-of-life software. With federal remediation deadlines of November 21 and December 2, 2026, and CVE-2026-90436 confirmed unpatched on an EoL library, organizations face immediate exposure across cloud workloads, AI inference pipelines, and NAS infrastructure.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

Apache Axis 1.x has reached end-of-life and will not receive an official vendor patch, leaving any application embedding the library—such as Atlassian Confluence with XML-RPC and SOAP APIs enabled—permanently exposed unless organizations migrate to a supported SOAP engine like Apache Axis 2 or apply the community commit patch.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

This incident involved unauthenticated RCE across four distinct internet-facing services, followed by rapid lateral movement into internal databases, cloud data warehouses, and SaaS platforms — exactly the kind of multi-vector, cross-environment attack that Aviatrix Zero Trust CNSF is designed to constrain. By enforcing workload-level segmentation, identity-aware access policies, and controlled egress paths, CNSF would likely have reduced the attacker's reachability and blast radius at nearly every stage of the chain.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Inline IPS enforcement with CVE-specific signatures could likely have detected and blocked inbound exploit traffic targeting these four vulnerable endpoints before code execution was achieved, reducing the attacker's ability to establish an initial foothold across any of the affected services.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust identity-based segmentation policies would likely have constrained the Confluence workload's ability to initiate direct connections to MySQL, the Crowd API, and Active Directory, reducing the scope of credential harvesting and limiting how far the attacker could elevate access from a single compromised service.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west enforcement at the workload and namespace level would likely have constrained the attacker's ability to pivot from a compromised on-premises workload into cloud data warehouse environments and SaaS platforms, reducing the lateral reach available after initial credential compromise.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Centralized traffic observability across cloud environments would likely have surfaced anomalous outbound connection patterns to ephemeral tunnel domains shortly after exploitation, giving operators visibility into C2 staging activity that would otherwise blend into normal HTTPS traffic.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement with FQDN-based outbound filtering would likely have blocked unauthorized data transfers to attacker-controlled Pinggy and Cloudflare Tunnel destinations, reducing the volume of credentials, payment card data, and configuration material successfully exfiltrated from compromised workloads.

Impact (Mitigations)

Had prior CNSF controls constrained lateral movement and egress paths, the attacker's operational surface at the impact stage would likely have been significantly narrower — with miner deployment, ransomware execution, and LLMjacking activity potentially limited to fewer workloads rather than spreading across cloud, on-premises, and SaaS environments.

Impact at a Glance

Affected Business Functions

  • Network Attached Storage (NAS) Data Services
  • Cloud and AI Inference API Management
  • Research Data Capture and Clinical Trial Platforms (REDCap)
  • Enterprise Collaboration and Workspace Platforms (Atlassian Confluence)
Operational Disruption

Estimated downtime: 14 days

Financial Impact

Estimated loss: N/A

Data Exposure

Multiple sensitive data categories are at risk across the affected organizations and sectors. Synology NAS victims face encryption and exfiltration of stored files including business documents, backups, and proprietary data via C3RB3R ransomware. Confluence Data Center victims experienced harvesting of database credentials, application tokens, VPN configurations, private keys, payment card numbers (filtered via Luhn checks), Active Directory user and group membership data via Atlassian Crowd API, and cloud data warehouse access through compromised Microsoft 365 service accounts. REDCap victims risk exposure of clinical research participant data, survey responses, and potentially protected health information (PHI). LLMjacking victims in financial services, retail, transportation, and technology sectors face unauthorized access to AI inference infrastructure, elevation of API credentials to administrative level, and potential exfiltration of proprietary AI model configurations. The multi-sector scope and confirmed credential harvesting, payment card hunting, and ransomware deployment collectively represent a high-severity data exposure event.

Recommended Actions

  • • Deploy Inline IPS (Suricata) with up-to-date signatures for CVE-2026-90436, CVE-2026-90817, CVE-2026-40217, and CVE-2024-10441 to detect and block unauthenticated RCE exploit traffic at the network perimeter before code execution reaches vulnerable application stacks.
  • • Enforce Zero Trust Segmentation with identity-based microsegmentation policies to prevent compromised application workloads (such as Confluence service accounts) from authenticating to internal databases, querying directory APIs like Atlassian Crowd, or accessing cloud data warehouses outside explicitly authorized service-to-service paths.
  • • Implement Egress Security and Policy Enforcement with FQDN filtering and data loss prevention controls to block outbound connections to ephemeral tunnel domains (Pinggy, Cloudflare Tunnel) used for C2 staging and to prevent unauthorized exfiltration of credentials, tokens, and payment card data to attacker-controlled destinations.
  • • Activate Multicloud Visibility and Control with centralized traffic observability and anomaly detection across hybrid and multi-cloud environments to identify suspicious lateral movement patterns, legacy authentication sign-ins from external IPs, and anomalous interactions with LLM inference APIs that indicate LLMjacking privilege escalation activity.
  • • Leverage Cloud Native Security Fabric (CNSF) with real-time inline enforcement and distributed policy to provide a unified prevention layer across all six kill chain stages, ensuring that AI-generated attacker scripts, in-memory loaders, cryptocurrency miners, and ransomware payloads are identified and contained before achieving persistent impact on NAS devices, Kubernetes workloads, or cloud data warehouses.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image