Confluence Axis Flaw Is Being Exploited: How to Check Your Server

Attackers exploited an Apache Axis flaw in Confluence Data Center. Check the Remote API, patch to a fixed release and investigate even requests that returned errors.
Server racks in a data center used to illustrate enterprise networking and security systems
Photo by Kevin Ache on Unsplash

Attackers have exploited a critical Apache Axis flaw in an Atlassian Confluence Data Center installation, using the server as a foothold to search for credentials and reach a cloud data warehouse, security company Rapid7 reported. The affected Confluence feature is disabled by default on newer installations, but older configurations and upgraded systems still need checking.

The vulnerability, CVE-2026-90436, can allow an unauthenticated remote attacker to run code when the legacy Remote API is enabled. Atlassian lists Confluence Data Center 9.2.28 as a fixed release; version 10 and later removed the affected feature. Atlassian Cloud is not affected, according to its security advisory.

Which Confluence installations need attention?

Atlassian identifies Data Center versions 1.x through 9.x as affected when Remote API (XML-RPC & SOAP) is enabled. The setting has been off by default for new installations since Confluence 3.0, but that does not establish the setting on a particular server. Check existing configuration, including internal servers and instances upgraded from older installations.

Prioritize internet-accessible servers. Update affected installations to the latest supported release or the fixed 9.2.28 LTS release, following Atlassian’s current upgrade guidance. Confluence 10.x and later and Atlassian-hosted Cloud sites are outside this specific exposure.

How to disable and test the Remote API

If an upgrade cannot be applied immediately, Atlassian provides a temporary mitigation:

  1. Sign in as a Confluence administrator and open General Configuration, then Further Configuration.
  2. Choose Edit, clear Remote API (XML-RPC & SOAP), and save. The change takes effect without a restart.
  3. Visit <base_url>/plugins/servlet/soap-axis1/confluenceservice-v2 on your own instance. Atlassian expects HTTP 403 Forbidden when the mitigation is working. If an AXIS service message appears instead, recheck the configuration and contact support.

Turning the API off can interrupt scripts, automation and third-party add-ons that depend on it. Identify those dependencies and test where practical, but treat an exposed vulnerable service as urgent. A 403 confirms the vendor’s mitigation check at that endpoint; it does not establish that a server was never compromised.

Why an HTTP 500 deserves investigation

In a case detected on November 13, Rapid7 found unauthenticated POST requests to the SOAP endpoint that returned HTTP 500 errors. Within seconds, endpoint telemetry showed the Confluence Java process launching Bash and curl under the Confluence service account. The error responses did not mean the attempted execution had failed.

Rapid7 reported that the intruder searched Confluence configuration, database contents and attachments for credentials. Roughly four hours after the initial request, the attacker used a service-account credential to query a production cloud data warehouse. Later, the attacker signed in to Microsoft 365 using an integration account and legacy authentication. These observations describe one investigated intrusion, not every exploitation attempt.

For exposed installations, retain and review Confluence and reverse-proxy access logs for requests to the SOAP endpoint, including HTTP 500 responses. Correlate those requests with endpoint records showing the Java service spawning shells or network utilities, unexpected outbound connections, and access to configuration files or credentials. Legitimate integrations and authorized scans can also create endpoint traffic, so a request alone is not proof of compromise.

Engage incident responders if evidence suggests execution or unauthorized access. Review the permissions and activity of credentials available to the Confluence service and stored in pages or attachments; revoke and replace exposed secrets through the relevant systems as the investigation warrants. Rapid7’s advisory provides observed indicators, but their absence does not rule out an intrusion.

The library reaches beyond Confluence

Apache Axis implements SOAP web services for Java. The flaw lies in the older Axis 1.x line: handling a crafted SOAP fault can instantiate a class selected by an attacker before its validity is checked, according to Italian cybersecurity guidance. Whether a particular application is exploitable depends on how it uses and exposes the library.

Axis 1.x is end-of-life, and Apache does not expect to issue a fixed 1.x release. Rapid7 advises migrating to a supported SOAP engine or using a build with the upstream patch applied. For commercial products that embed Axis, follow each vendor’s own fixes rather than replacing a library blindly.

N-able N-central also uses the affected library in its legacy API. Its remediation has separate server, Agent and Probe requirements; see our N-central Hotfix 3 guide for those details.

Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
Google Gemini Spark app image representing Chrome auto-browse access for browser agents

Gemini Tasks Is Free in Six Countries: How to Start and Control Its Access

Related Posts