Cybersecurity
Apache Axis Flaw Exploited: Patch Confluence and N-central
Affix Center · · 6 min read

In short: A critical flaw in Apache Axis 1.x, tracked as CVE-2026-90436, is being exploited against Atlassian Confluence Data Center and N-able N-central. Attackers can run commands without logging in when an old SOAP API is switched on. Atlassian and N-able have released fixes, and Indian organisations using either product should patch or disable the API now.
What Happened
According to Rapid7's report published on 16 November 2026, the Apache Software Foundation disclosed the vulnerability in Apache Axis 1.x on 6 November 2026. Apache Axis is an old, end-of-life library for SOAP web services that is still bundled inside some enterprise products. The flaw is an unsafe reflection bug that can let an attacker run code on the server without signing in. CISA scores it 9.8 out of 10, while Atlassian rates it 9.3 under CVSS 4.0.
Atlassian published its security advisory for Confluence Data Center on 9 November 2026 (US time). A public proof-of-concept exploit targeting N-able N-central appeared on 12 November. On 13 November, Rapid7 detected exploitation against a Confluence Data Center customer, and N-able reported attacks on N-central the same day. SecurityWeek reported on 17 November that N-able had released N-central 2026.4 Hotfix 3 on 16 November, fixing 17 vulnerabilities and permanently blocking legacy APIs. Several security news sites reported that CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 18 November.
Rapid7's description of the Confluence intrusion is a warning for every organisation. Within minutes, the attacker was searching wiki pages and attachments for passwords, tokens, VPN configurations and private keys. Hours later, they used a service account found this way to reach a cloud data warehouse and then signed in to Microsoft 365 as an integration account.
Who Is Affected
Based on the vendor advisories and Rapid7's report:
- Atlassian Confluence Data Center 1.x to 9.x, but only when the "Remote API (XML-RPC & SOAP)" setting is enabled. Version 9.2.28 contains the fix. Atlassian says Confluence 10.x is not affected, and Atlassian Cloud sites are not affected.
- N-able N-central deployments with the Legacy API enabled. The fix is N-central 2026.4 HF3. N-able says hosted environments are already patched, but Agents and Probes still need upgrading.
- Any other product or in-house application that bundles Apache Axis 1.x (up to 1.4). Apache does not plan a new 1.x release, so the advice is to move to another SOAP engine such as Axis2 or apply the community patch.
What It Means for Indian Businesses and Departments
Confluence is widely used as an internal wiki by IT companies, banks, product teams and some government projects in India. N-central is a remote monitoring and management tool used by managed service providers and IT teams to control large numbers of computers, so a compromise there can reach every managed device.
The bigger lesson is about what sits inside these systems. Wikis often hold passwords and configuration details pasted years ago. Once an attacker reads them, patching the server alone does not undo the damage. Organisations covered by CERT-In's directions should also remember that certain cyber incidents must be reported to CERT-In within six hours of being noticed.
What to Do Now
- Find affected systems. List every Confluence Data Center and N-central server, including test and internal ones, and ask software vendors whether their products bundle Apache Axis 1.x.
- Patch Confluence. Upgrade Confluence Data Center to 9.2.28 or a current 10.x release, as Atlassian advises.
- Disable the Remote API if you cannot patch today. In Confluence, turn off "Remote API (XML-RPC & SOAP)" under General Configuration. Atlassian notes this needs no restart but may break scripts and add-ons that use it.
- Update N-central fully. Upgrade on-premises N-central servers to 2026.4 HF3, then upgrade all Agents and Probes, and confirm the Legacy API is blocked.
- Look for signs of compromise. Check web and system logs for unusual SOAP requests and unexpected processes, and use the indicators published by Rapid7. A clean result does not prove a system was untouched.
- Rotate exposed secrets. Change passwords, API tokens and service account keys stored in Confluence pages or used by N-central, and move secrets into a proper password vault.
- Report and record. If you find evidence of an incident, follow your incident response plan and check whether CERT-In reporting applies.
Frequently Asked Questions
Is Confluence Cloud affected by CVE-2026-90436?
No. Atlassian says its Cloud sites are not affected. The issue affects self-managed Confluence Data Center versions 1.x to 9.x when the Remote API is enabled.
Is turning off the Remote API enough?
It is a temporary mitigation that blocks the attack path. You should still upgrade to a fixed version and check whether the server was attacked before the setting was changed.
We use an IT provider who manages our PCs. Should we ask them?
Yes. Ask whether they use N-central or any tool that bundles Apache Axis 1.x, whether it is patched to the fixed version, and whether they have checked for compromise.
For a lasting routine rather than one-off fixes, read our guide to the patch management process, and see our recent alert on the Java4Shell Java flaw, which also affects widely used enterprise platforms.
How Affix Center Can Help
Affix Center Softech Services in Mumbai helps businesses and government departments find exposed systems, patch them safely and check for signs of compromise. Our VAPT services in Mumbai can test your Confluence, portals and APIs after patching, and our cyber security services team can help with log review, secret rotation and monitoring. To get help with this issue, contact us.