How to Disable the Confluence Remote API Safely
Step by step: disable the Confluence Remote API (XML-RPC and SOAP), verify the 403 response, check integrations and plan the upgrade to a fixed build.
To disable the Confluence Remote API, sign in as an administrator, open General Configuration, then Further Configuration, click Edit, clear "Remote API (XML-RPC & SOAP)" and save. Atlassian says the change takes effect immediately, with no restart. It is the interim mitigation for Confluence CVE-2026-90436, an exploited remote code execution flaw, until you can upgrade to 9.2.28 or a 10.x release.
What is the Confluence Remote API?
The Confluence Remote API is the legacy XML-RPC and SOAP interface that older scripts and add-ons used to read and change Confluence content. It runs on the Apache Axis 1.x library.
Atlassian turned it off by default for new installations starting in Confluence 3.0 and removed it completely in Confluence 10.0. Instances that still have it enabled are usually old servers upgraded in place, or servers where someone switched it on for an integration years ago.
Who needs to do this
Every team running Confluence Data Center 1.x through 9.x on their own infrastructure. Atlassian Cloud sites are not affected and need no action.
If your instance is already on 9.2.28 or a 10.x release, the CVE-2026-90436 risk is addressed. Disabling an unused API is still good hygiene on any version that has it.
Before you change anything
The Remote API exists because something once needed it. Atlassian warns that turning it off may break scripts, automations and third-party add-ons. Spend ten minutes finding out what depends on it:
- Ask integration owners. Reporting scripts, migration tools, backup tools and older chat integrations are common users of XML-RPC and SOAP.
- Check add-ons. Review installed apps for anything old that predates Confluence's REST API.
- Test in staging first if you have one. Atlassian recommends a non-production test.
If you find a dependency, do not leave the API on to keep it working. With exploitation confirmed by Rapid7, the safer order is to disable the API now, accept the broken integration, and move it to the REST API.
How do you disable the Confluence Remote API?
Clear the "Remote API (XML-RPC & SOAP)" checkbox in Further Configuration and save the page. No restart is required.
Step by step, from Atlassian's advisory:
- Sign in to Confluence as an administrator.
- Click the gear icon in the top right, then General Configuration, then Further Configuration. You can also go straight to
<base_url>/admin/viewspacesconfig.action. - Click Edit on the far right.
- Clear the checkbox for Remote API (XML-RPC & SOAP).
- Click Save at the bottom of the page.
- When the page reloads, confirm the checkbox is still clear.
Repeat this on every Confluence instance, including test, staging and disaster recovery copies. A forgotten staging server with production data is still a breach.
How do you check that the Remote API is really off?
Request the Axis service endpoint and confirm it returns HTTP 403 Forbidden. Any other response means the API is still reachable.
Atlassian's verification step is to browse to:
<base_url>/plugins/servlet/soap-axis1/confluenceservice-v2
Expected result: "HTTP Status 403 - Forbidden." If the page mentions "confluenceservice-v2" or "AXIS service," the setting did not take. Go back through the steps above, and contact Atlassian Support if it still fails.
Run this check from outside your network as well as inside. A reverse proxy or load balancer in front of Confluence should also return the 403, not a cached page.
After the mitigation: upgrade
Disabling the API reduces exposure. Atlassian is clear that it does not fix the underlying vulnerability. Plan the upgrade:
- On 9.2.x: upgrade to 9.2.28, the fixed build Atlassian lists.
- On older branches: move to the latest release or a fixed LTS release. Atlassian no longer ships binary patches.
- On 10.x: the Remote API is gone. Nothing to disable.
Record the change in your change log with the date, the instance names and the verification result. If an auditor or incident responder asks later when the exposure ended, you will have an answer.
Check for compromise on exposed servers
If an instance had the Remote API enabled and was reachable from the internet after November 6, 2026, treat it as possibly compromised. Atlassian says it cannot confirm whether customer instances were affected.
- Search proxy, firewall and web server logs for the IP addresses Rapid7 published in its write-up (listed in our news coverage). No hits does not mean the server is clean.
- Look for unexpected processes or outbound connections from the Confluence service account.
- Review recent changes to administrator accounts and installed apps.
- Rotate secrets that the Confluence server could read, such as database credentials and integration tokens, if you find anything suspicious.
The underlying weakness is explained in what unsafe reflection is and why it leads to code execution. For the planning side, see why you should switch off unused legacy APIs.