Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
A.I. Cyber Security / Infrastructure & Data

Rapid7 Confirms Active Exploitation of Apache Axis RCE Flaw CVE-2026-90436 in Confluence and N-central

Rapid7 MDR observed unauthenticated exploitation of CVE-2026-90436 against Atlassian Confluence Data Center via SOAP Axis 1.x endpoints returning HTTP 500 while spawning Bash and curl, alongside active N-able N-central attacks.

Listen to this articleBrowser Voice
Ready
Official company logo or product image for rapid7-confirms-cve-2026-90436-exploitation-confluence-n-central
Official image or organization logo from www.rapid7.com; identification only, no endorsement.
Event / context: 2026-11-16. Source check: October 28, 2026.

Active Exploitation of CVE-2026-90436 Expands Across Enterprise Platforms

Rapid7 has confirmed active in-the-wild exploitation of CVE-2026-90436, a critical unauthenticated remote code execution flaw originating in Apache Axis 1.x, targeting both Atlassian Confluence Data Center and N-able N-central deployments. According to a Rapid7 Emergent Threat Response report published on November 16, 2026, and updated on November 17, 2026, threat actors began operationalizing the vulnerability within days of its public disclosure. Rapid7 recommends that organizations remediate exposed systems on an emergency basis outside of normal patching cycles.

The timeline illustrates how rapidly upstream open-source library vulnerabilities cascade into downstream enterprise infrastructure. The Apache Software Foundation initially disclosed CVE-2026-90436 on November 6, 2026, identifying an unsafe reflection bug tracked as CWE-470 inside Axis 1.x. CISA subsequently assigned the flaw a CVSS score of 9.8 Critical. Less than a week later, on November 12, 2026, a proof-of-concept exploit leveraging CVE-2026-90436 against N-able N-central appeared publicly as part of a series of zero-day disclosures targeting the platform. On November 13, 2026, Rapid7 Managed Detection and Response (MDR) analysts observed live exploitation against an Atlassian Confluence Data Center instance in a customer environment, while N-able separately reported active exploitation against N-central for a flaw strongly correlating to the same Apache Axis weakness.

Apache Axis 1.x Architecture and Observed Server Telemetry

Apache Axis is a legacy Simple Object Access Protocol (SOAP) implementation built for creating Java Web services. When downstream enterprise applications embed Axis 1.x to support SOAP integrations, they inherit its request-handling and reflection pathways. Because CVE-2026-90436 stems from unsafe reflection (CWE-470), an unauthenticated attacker capable of reaching an exposed Axis 1.x SOAP endpoint can manipulate runtime class resolution and achieve remote code execution without valid credentials. Notably, Rapid7 specifies that both Atlassian Confluence Data Center and N-able N-central require a non-default configuration to expose the vulnerable code path.

Endpoint and web access telemetry captured during the November 13, 2026 incident provides concrete forensic indicators of how the exploit behaves in practice. Rapid7 MDR initially received a surge of alerts triggered by abnormal child processes spawned by a Confluence server. Inspecting Confluence HTTP access logs revealed unauthenticated POST requests directed at the endpoint /plugins/servlet/soap-axis1/confluenceservice-v2. Crucially, every malicious POST request returned an HTTP 500 Internal Server Error response to the caller. Despite those apparent server-side failures at the HTTP layer, endpoint detection telemetry confirmed that Confluence's Java process successfully executed child processes, specifically launching Bash and curl under the dedicated confluence service account.

Detection Blind Spots and Operational Workflow Impact

For security operations teams, system administrators, and DevSecOps engineers, the discrepancy between HTTP status codes and actual operating system execution carries immediate operational consequences. Defenders who triage web server logs by filtering out HTTP 500 responses or assuming an Internal Server Error indicates a failed exploit attempt risk overlooking active compromises on Java middleware. Because the unsafe reflection payload triggers execution inside the Java process before or during exception handling, the servlet container logs a failure even as Bash and curl spawn beneath the confluence service user.

Beyond log triage, the incident underscores the maintenance burden of transitive SOAP dependencies in large Java ecosystems and remote monitoring and management (RMM) platforms. Engineering teams maintaining self-hosted Confluence Data Center instances must audit whether legacy SOAP plugins or Axis 1.x servlets were enabled historically for third-party integrations, as non-default configurations frequently persist across years of upgrades. Similarly, managed service providers operating N-able N-central face heightened urgency due to the availability of a public proof-of-concept exploit since November 12, compressing the window between patch availability and automated scanning or opportunistic intrusion.

Rapid7's guidance to patch outside standard maintenance windows reflects the high stakes of unauthenticated RCE on collaboration servers and RMM appliances. Both Confluence Data Center and N-central typically hold sensitive operational knowledge, credentials, or administrative pathways into connected environments, making rapid containment and process-level hunting for unexpected Java child processes essential.

Configuration Caveats and Disclosure Boundaries

Several technical and reporting boundaries remain important for defenders assessing exposure. First, CVE-2026-90436 does not automatically render every Atlassian Confluence Data Center or N-able N-central deployment exploitable out of the box; Rapid7 notes that only certain versions running a non-default configuration are affected. Organizations must therefore inspect active servlet mappings and product-specific advisories rather than relying solely on inventory version checks.

Second, while Rapid7 MDR directly verified CVE-2026-90436 exploitation in a Confluence Data Center customer environment, the correlation between N-able's November 13 wild-exploitation notice and CVE-2026-90436 is described as strong rather than confirmed identical in every detail within the initial summary, alongside the November 12 N-central proof-of-concept disclosure. Finally, exact vulnerable version ranges, granular firewall rules, and network indicators of compromise are governed by Rapid7's full advisory updates, and teams should verify official vendor guidance from Apache, Atlassian, and N-able before applying configuration changes or emergency upgrades.

Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.

Follow your curiosity.

Pass the signal.