Critical Apache Axis RCE Flaw (CVE-2026-90436) Exploited

Critical Apache Axis RCE Flaw Actively Exploited in N-able, Atlassian

CRITICAL
November 17, 2026
5m read
VulnerabilityPatch ManagementCyberattack

Related Entities

Products & Tech

Apache Axis Confluence Data CenterN-central

CVE Identifiers

CVE-2026-90436
CRITICAL
CVSS:9.8

Full Report

Executive Summary

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.


Vulnerability Details

  • CVE ID: CVE-2026-90436
  • Severity: Critical (CVSS 9.8)
  • Vulnerability Type: Unsafe Reflection
  • Impact: Unauthenticated Remote Code Execution (RCE)

The 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.


Affected Systems

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:

  • Atlassian Confluence Data Center: Vulnerable in a non-default configuration.
  • N-able N-central: Vulnerable in a non-default configuration.

Any other application or service that utilizes the Apache Axis 1.x library is also potentially vulnerable and should be investigated.


Exploitation Status

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.


Impact Assessment

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:

  • Installation of ransomware or other malware.
  • Theft of sensitive data stored on or accessible from the compromised server.
  • Use of the server as a pivot point to attack other systems within the internal network.
  • Disruption of business operations that rely on the affected Confluence or N-central instances.

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.


Cyber Observables — Hunting Hints

The following patterns may help identify vulnerable or compromised systems:

Type
url_pattern
Value
/services/
Description
Default path for Apache Axis web services. Exploitation attempts will likely target URLs under this path.
Context
Web server logs (IIS, Tomcat, etc.), WAF logs.
Confidence
medium
Type
network_traffic_pattern
Value
Inbound SOAP requests containing <methodName>invoke
Description
The unsafe reflection may be triggered via the invoke method in a SOAP request.
Context
Network Intrusion Detection Systems (NIDS), WAF logs with payload inspection.
Confidence
medium
Type
file_name
Value
axis.jar
Description
The presence of this JAR file indicates the use of the Apache Axis library.
Context
Endpoint file system scans, software bill of materials (SBOM).
Confidence
high

Detection Methods

  • Vulnerability Scanning: Use a vulnerability scanner with updated plugins to identify systems running a vulnerable version of Apache Axis, Atlassian Confluence, or N-able N-central.
  • Log Analysis: Scrutinize web server access logs for unusual POST requests to SOAP endpoints, especially those that result in 500 server errors, which can indicate a failed exploit attempt. This is a form of D3-WSAA: Web Session Activity Analysis.
  • File Integrity Monitoring: Monitor for the creation of unexpected files (e.g., web shells, executables) in the directories of the web application, which would indicate a successful RCE.

Remediation Steps

Due to active exploitation, remediation should be treated as an emergency.

  1. Apply Vendor Patches: Atlassian and N-able have released patches and mitigation guidance for their respective products. These should be applied immediately.
  2. Isolate: If patching is not immediately possible, isolate the vulnerable systems from the internet by blocking access at the network perimeter. This is not a long-term solution.
  3. Migrate from Axis 1.x: For custom applications using Apache Axis 1.x, the official recommendation is to migrate to a modern, supported SOAP engine like Apache CXF. If migration is not feasible, Apache has provided a patch that can be manually applied to the source code.
  4. Hunt for Compromise: Assume that any publicly exposed, unpatched system has been compromised. Conduct a thorough investigation, reviewing logs and looking for indicators of attacker activity, persistence mechanisms, or lateral movement.

Timeline of Events

1
November 6, 2026
The Apache Software Foundation discloses CVE-2026-90436.
2
November 12, 2026
A proof-of-concept exploit for N-central is published.
3
November 13, 2026
Rapid7 detects active exploitation of the vulnerability against an Atlassian Confluence customer.
4
November 13, 2026
N-able confirms active exploitation against its N-central product.
5
November 17, 2026
This article was published

MITRE ATT&CK Mitigations

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.

D3FEND Defensive Countermeasures

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.

Timeline of Events

1
November 6, 2026

The Apache Software Foundation discloses CVE-2026-90436.

2
November 12, 2026

A proof-of-concept exploit for N-central is published.

3
November 13, 2026

Rapid7 detects active exploitation of the vulnerability against an Atlassian Confluence customer.

4
November 13, 2026

N-able confirms active exploitation against its N-central product.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

CVE-2026-90436Apache AxisRCEZero-DayAtlassian ConfluenceN-able N-centralRapid7Vulnerability

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.