Home/ Blog/ Security news/ Article
Blog · Security news

Confluence CVE-2026-90436: Exploited Axis RCE, Patch to 9.2.28

CVE-2026-90436, an Apache Axis 1.x flaw, is exploited against Confluence Data Center with the Remote API on. Patch to 9.2.28, disable SOAP, check IOCs.

Dark title card reading Confluence under attack through old Axis library

Attackers are already using CVE-2026-90436 against Atlassian Confluence Data Center. If your Confluence has the Remote API (XML-RPC and SOAP) setting turned on, treat it as an emergency. Upgrade to 9.2.28 or a 10.x release today. If you cannot upgrade yet, switch the setting off now.

Rapid7's managed detection team caught an attack on a customer's Confluence server on November 13, 2026. On the same day, N-able reported in-the-wild exploitation against N-central, its remote IT-management console. Rapid7 says the N-central bug strongly correlates with this CVE. Neither product has its own bug here. Both ship Apache Axis 1.x, a SOAP library that has been end-of-life for years, and the flaw is in that library. That changes what you have to check. Patching Confluence and N-central covers two products. It says nothing about the rest of your Java estate.

What is CVE-2026-90436, and why does a library bug reach so far?

CVE-2026-90436 is an unsafe reflection flaw (CWE-470) in Apache Axis 1.x, through version 1.4. An unauthenticated attacker can send a crafted SOAP fault message and make the server load and instantiate a Java class the attacker names. With the right class on the classpath, that becomes remote code execution (RCE).

Apache published the issue on oss-security on November 6. The bug lives in the code that reads the error details inside a fault. Axis honors a class name in the fault's detail block, and loading a class in Java runs its static initializer. That one load can be enough to run code. José Apari-Pantigozo of OKIOK is credited with the find. Axis 1.x is unsupported, and the project says it does not plan a fixed 1.x release. It points users to Axis 2/Java or to a patch commit they can apply to their own build.

Severity scores differ by source. The CISA-supplied CVSS 3.1 score is 9.8. Atlassian's own CVSS 4.0 assessment is 9.3, also critical. CVE-2026-90436 was not in CISA's Known Exploited Vulnerabilities (KEV) catalog when we checked on November 17. Rapid7's report predates any KEV listing, so do not wait for one.

CVE-2026-90436: from library advisory to live attacksNov 6: Axis flaw disclosed. Nov 9: Atlassian advisory. Nov 12: N-central PoC public. Nov 13: Confluence attacked. Nov 16: Rapid7 report.CVE-2026-90436: from library advisory to live attacksNov 6Axis flawdisclosedNov 9AtlassianadvisoryNov 12N-central PoCpublicNov 13ConfluenceattackedNov 16Rapid7 report
Sources: Apache Axis advisory (oss-security), Atlassian advisory, Rapid7. Dates are 2026.

The gap is the point. Six days passed between the library advisory and a public N-central exploit on November 12. Atlassian's fix landed in between, and the first confirmed Confluence attack came one day after the exploit went public. If your patch cycle is monthly, it would have missed all of that.

Which Confluence and N-central servers are exposed?

On the Confluence side, the Atlassian advisory covers Data Center from 1.x through 9.x. The fixed release is 9.2.28. Confluence 10.x and later are not affected, and Rapid7 notes those versions dropped the feature entirely. Atlassian Cloud sites are not affected. The flaw is only reachable when an administrator has enabled the Remote API (XML-RPC and SOAP) option. That option has been off by default on new installs since Confluence 3.0.

That default narrows who is exposed, but not in a comforting way. A server with the setting on is probably an older install that was upgraded many times and wired into scripts, add-ons or a migration tool years ago. Those integration-heavy instances are often the ones teams avoid upgrading. They are also the ones most likely to still sit on an old 7.x or 8.x line.

For N-central, the path in is the Legacy API, which is also not on by default. N-able's guidance, as summarized by Rapid7, is to confirm Legacy API is disabled, even on 2026.4 HF2. The 2026.4 HF3 release removes Legacy API access for good. N-able had finished the hosted upgrades by its November 16 notice, and on-premises availability was still being finalized at that point. Rapid7 also says N-able temporarily disabled the Intune integration on hosted N-central as a precaution. It follows other recent N-central security events, including the CVSS 10 code-execution fix in September and the Storm-1175 ransomware intrusions through the console before that.

Why a login on the SOAP service does not protect you

Many teams think a SOAP endpoint is safe once its service needs credentials. That does not hold for this bug. The Apache advisory says Axis parses the fault before any per-service handler chain runs, so authentication handlers configured on a service never get a chance to reject the request. A public lab repository on GitHub that reproduces the flaw on stock Axis 1.4 reports the same behavior. It fires against any Axis URL, including service names that are not deployed.

The practical consequences are concrete. You cannot mitigate by putting a password on the web service. Removing the one service you think is sensitive does not help either. The real controls are not running the vulnerable Axis code, turning off the feature that exposes it, or blocking the Axis paths before requests reach the application. The same lab notes that stock Axis on its own only gives class instantiation, and that code execution needs a usable class from the host application. The reported attacks against Confluence and N-central suggest both provide one. Your in-house app might as well, and you should not bet that it does not.

Detection: the Confluence endpoint check and Rapid7's indicators

Atlassian gives one direct test for whether the Remote API mitigation is working. Once the setting is off, the SOAP path below should return HTTP 403 Forbidden. The IP addresses are the indicators Rapid7 published. The Confluence set comes from its own detections, and the N-central set comes from N-able's November 13 update for customers who had not disabled Legacy API. Rapid7 warns that finding none of them does not prove a server is clean.

CVE-2026-90436: Confluence mitigation check, Axis 1.x jar search, and published source IPs
https://<confluence-base-url>/plugins/servlet/soap-axis1/confluenceservice-v2
expected after mitigation: HTTP Status 403 - Forbidden
find / -xdev -name 'axis*.jar' 2>/dev/null
Confluence exploitation sources (Rapid7):
192.238.253[.]176
5.133.47[.]243
163.182.68[.]109
104.13.106[.]166
N-central exploitation sources (N-able, via Rapid7):
157.20.241[.]16
139.99.69[.]109
79.76.51[.]56

Search your reverse proxy and Tomcat access logs for soap-axis1 requests, going back to at least November 6. The results serve two purposes. Requests from the addresses above are a reason to open an incident. Requests from your own integration hosts tell you which scripts will break when you turn the Remote API off, so you know what to fix before you flip it. The find line is a starting inventory, not a verdict. Jar names vary between products, and some applications repackage Axis classes inside a larger archive.

Turn off the Remote API before you schedule the upgrade

On Confluence, an administrator can disable the setting from the gear menu: General Configuration, then Further Configuration, then Edit. Clear "Remote API (XML-RPC & SOAP)" and save. Atlassian says no restart is needed. Afterwards, check that the endpoint above returns 403. Then move to 9.2.28 or a current 10.x release, so a later configuration change cannot reopen the hole. Expect broken automations, and use the access-log search above to find them in advance.

On N-central, confirm Legacy API is disabled using N-able's instructions, then follow its Agent and Probe upgrade guidance for both hosted and on-premises deployments. Whichever product you run, if the vulnerable setting was on and the server faced the internet at any point since November 6, patching only closes the door. You still need to look for what may have come through it: new admin accounts, unexpected child processes of the Java service, and outbound connections from the application host. Rapid7 advises treating exposed systems as an emergency outside normal patch cycles.

The harder question: what else in your stack still ships Axis 1.4?

Confluence and N-central are the two products confirmed so far, not the full list. Axis 1.x was the default way to build Java SOAP services for most of the 2000s. It still turns up in vendor appliances, old line-of-business apps, and internal services nobody has touched in a decade. Because Apache will not release a fix, no package update will clean those copies for you. Each vendor has to rebuild its product, and each in-house app has to be patched or ported by whoever owns it now.

That makes this a software inventory problem more than a patching problem. If you can say within an hour which hosts carry an Axis 1.x jar, this week is manageable. If you cannot, that gap is the risk to close, and it will matter again for the next flaw in an abandoned library. See our notes on vulnerability detection for how we think about that visibility.

Topics

Frequently asked questions

What is CVE-2026-90436?

CVE-2026-90436 is a critical unsafe reflection flaw in Apache Axis 1.x, an end-of-life Java SOAP library. A crafted SOAP fault lets an unauthenticated attacker make the server load and instantiate a class they choose, which can lead to remote code execution. It affects Axis 1.x through 1.4.

Is CVE-2026-90436 being exploited in the wild?

Yes. Rapid7 reports that its managed detection team saw exploitation against Atlassian Confluence Data Center on November 13, 2026. N-able reported in-the-wild exploitation of N-central on the same day, which Rapid7 says strongly correlates with this CVE. A proof-of-concept targeting N-central went public on November 12.

Which Confluence versions are affected and which version fixes it?

Atlassian lists Confluence Data Center 1.x through 9.x as affected when the Remote API (XML-RPC and SOAP) setting is enabled. Version 9.2.28 contains the fix, and Confluence 10.x and later are not affected. Atlassian Cloud sites are not impacted and need no action.

How do I mitigate CVE-2026-90436 on Confluence without upgrading?

Disable the Remote API (XML-RPC and SOAP) option under General Configuration and Further Configuration, then save. Atlassian says no restart is required. Confirm the change by checking that the soap-axis1 confluenceservice-v2 path returns HTTP 403. Expect scripts and add-ons that use the API to stop working.

Does requiring authentication on an Axis SOAP service block this attack?

No. According to the Apache advisory, Axis parses the incoming SOAP fault before any per-service handler chain runs, so service-level authentication handlers never see the request. Mitigation has to remove the vulnerable code path, turn off the exposing feature, or block the Axis URLs upstream.

Will Apache release a fixed version of Axis 1.x?

No. The Apache Axis project says it does not expect to publish an Axis 1.x release for this flaw because the branch is end-of-life. It recommends migrating to another SOAP engine such as Axis 2/Java, or applying the published patch commit to your own Axis build.

See what Suriq finds on your own servers.

Agentless checks for uptime and your cloud, a lightweight agent for detection on each server, and one console that ranks and explains what it finds.