- Enterprise
· ASC Editorial Team
One Old Library, Two Exploited Products: Confluence Joins N-central in the Apache Axis Attacks
On 16 November 2026, Rapid7 reported attackers exploiting CVE-2026-90436 in Atlassian Confluence Data Center. The same flaw appears to be behind the attacks on N-able's N-central that we covered in our N-central article.
The flaw is in Apache Axis 1.x, an old Java library for SOAP web services that other products build in. Apache disclosed it on 6 November. It lets an attacker run code on the server without logging in, and CISA rates it 9.8 out of 10. Axis 1.x reached the end of its life years ago, and Apache doesn't plan to release a fixed version. Each product that includes it has to fix it in its own code.
Rapid7 saw the attack on 13 November, when a customer's Confluence server started running shell commands. The requests went to Confluence's SOAP interface and needed no login. Over the following hours the attacker: - queried Confluence's database; - searched attachments for passwords and card numbers; - went after the domain controller to collect password hashes; - signed in to Microsoft 365 using legacy authentication, about 12 hours after getting in.
Atlassian's advisory rates the flaw critical. It affects Confluence Data Center and Server up to version 9.2.27, but only when the "Remote API (XML-RPC & SOAP)" setting is switched on. That setting has been off by default for new installations since Confluence 3.0. Version 9.2.28 fixes it, Confluence 10.0 removed the feature, and Atlassian Cloud is not affected. Atlassian's advisory doesn't say whether it has seen attacks. Rapid7 is the source for that. N-able released N-central 2026.4 Hotfix 3 on 16 November, which turns off the Legacy API that the N-central attacks used.
Two lessons stand out. The first is one we made in Patched but Exposed. Both products were vulnerable only because a non-default feature had been switched on. The second is newer. One old library sat inside two unrelated products, and their customers could do nothing about it until each vendor shipped a fix. Most organisations have no list of the components inside the software they buy, so they find out about flaws like this from the news.
If you run Confluence Data Center or Server: - Upgrade to 9.2.28 or a current 10.x release. - If you can't upgrade straight away, turn off "Remote API (XML-RPC & SOAP)" under General Configuration → Further Configuration. It takes effect without a restart, but integrations that use it will stop working. - Then check whether anyone got in. Look for: - requests to `/plugins/servlet/soap-axis1/` in the access logs; - Confluence's Java process starting a shell or curl; - unexpected database logins with Confluence's credentials; - legacy-authentication sign-ins to Microsoft 365. - Block legacy authentication in Microsoft 365 if you haven't already.
For everything else you run, ask your main software vendors two questions. Which end-of-life components do their products include? Will they give you a software bill of materials, so you can check for yourself next time?
If a library inside one of your products reached end of life tomorrow, would anyone tell you?
Source: Rapid7: Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.