A critical vulnerability in Apache Axis 1.x, an end-of-life SOAP implementation, is under active exploitation. The vulnerability, tracked as CVE-2026-90436 with a CVSS score of 9.8, allows for unauthenticated remote code execution (RCE). Security researchers at Rapid7 have detected attackers exploiting this flaw against instances of Atlassian Confluence Data Center. Separately, N-able has confirmed its N-central product is also being targeted. Given the availability of a proof-of-concept (PoC) exploit and confirmed in-the-wild attacks, this vulnerability poses an immediate and severe risk to exposed organizations, necessitating emergency patching.
CVE-2026-90436The flaw exists in Apache Axis versions 1.x through 1.4. The library has reached its end of life, and the Apache Software Foundation has stated it will not release an official fix. The vulnerability can be triggered by a specially crafted SOAP request, allowing an attacker to execute arbitrary code on the server with the privileges of the web service user.
The vulnerability is not in the end products themselves, but in the shared Apache Axis library they use. The following products are confirmed to be affected and targeted:
Any other application or service that utilizes the Apache Axis 1.x library is also potentially vulnerable and should be investigated.
Active exploitation has been confirmed in the wild. Rapid7's Managed Detection and Response (MDR) team observed exploitation against a customer's Atlassian Confluence instance on November 13, 2026. On the same day, N-able issued a security advisory confirming active exploitation against its N-central product. A proof-of-concept exploit for N-central was publicly released on November 12, 2026, which has likely fueled the attacks. The vulnerability has been added to CISA's Known Exploited Vulnerabilities (KEV) catalog.
Successful exploitation of CVE-2026-90436 results in full remote code execution on the affected server. This allows an attacker to take complete control of the system, leading to potential outcomes such as:
Given that these products are often used to manage critical IT infrastructure and store important corporate knowledge, a compromise can have a devastating business impact.
The following patterns may help identify vulnerable or compromised systems:
/services/<methodName>invokeinvoke method in a SOAP request.axis.jar500 server errors, which can indicate a failed exploit attempt. This is a form of D3-WSAA: Web Session Activity Analysis.Due to active exploitation, remediation should be treated as an emergency.
Apply vendor-supplied patches for affected products like Atlassian Confluence and N-able N-central on an emergency basis.
If patching is not immediately possible, restrict network access to the vulnerable application from the internet.
Use a Web Application Firewall (WAF) or Intrusion Prevention System (IPS) with signatures for CVE-2026-90436 to block exploit attempts at the network edge.
The most critical and effective countermeasure for CVE-2026-90436 is to apply the security updates provided by Atlassian and N-able immediately. Given that this is a critical, unauthenticated RCE vulnerability under active exploitation, this action should be treated as an emergency. Organizations must activate their out-of-band patching procedures. Before deployment, test the patch in a staging environment to ensure it doesn't disrupt business operations. After deployment, verify that the patch was successfully applied by checking the product version number or using a vulnerability scanner. For custom applications using the vulnerable Apache Axis library, the 'Software Update' involves a more complex migration to a supported library like Apache CXF, which should be prioritized as a strategic project.
As a compensating control or a defense-in-depth measure, Inbound Traffic Filtering can be used to block exploitation attempts against CVE-2026-90436. This can be implemented using a Web Application Firewall (WAF) or an Intrusion Prevention System (IPS). Security teams should deploy virtual patches or custom rules that inspect inbound SOAP requests for patterns indicative of the exploit. This might include filtering requests to specific vulnerable endpoints (e.g., /services/AdminService) or blocking requests that contain signatures associated with the unsafe reflection technique. While this can be effective, it may not be foolproof and should be used in conjunction with patching, not as a replacement. It is particularly valuable as a temporary measure to protect systems while patching is being planned and executed.
The Apache Software Foundation discloses CVE-2026-90436.
A proof-of-concept exploit for N-central is published.
Rapid7 detects active exploitation of the vulnerability against an Atlassian Confluence customer.
N-able confirms active exploitation against its N-central product.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.