Apache Axis 1 Flaw Hits KEV: No Patch, Check Confluence
CISA added Apache Axis CVE-2026-90436 to KEV. Axis 1 is end of life with no fix, and Rapid7 saw Confluence hit. Here is what to check and what to retire.

There is no patch for this one, so the job is finding every place Axis 1 still runs and removing the exposure. CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalog, citing active exploitation. It is an unsafe reflection flaw in Apache Axis that lets an unauthenticated remote attacker run code. The Hacker News reports Axis 1.x is end of life, so no fix is coming.
What changed
The KEV listing follows two exploitation reports. The Hacker News says the flaw was used alongside the 4EverAble2Shell bugs in N-able N-central to deploy cryptocurrency miners. Rapid7 also saw it used against Atlassian Confluence Data Center in a customer environment, because Confluence uses the Axis library in its XML-RPC and SOAP APIs. Rapid7 flagged that incident on November 13.
Atlassian says an instance is only vulnerable if the “Remote API (XML-RPC & SOAP)” setting is enabled. That setting has been off by default for new installs since Confluence 3.0, and the feature was removed entirely in Confluence 10.0.
What Rapid7 saw after the foothold
Per The Hacker News summary, the attackers ran shell commands and scripts pulled from temporary Pinggy and Cloudflare Tunnel domains, then surveyed the environment. About three minutes after the first execution they were using Confluence’s own database credentials to read page bodies, application links and attachments with names suggesting credentials, tokens, VPN configs and private keys. They also tried to harvest Kerberos credentials, which failed, but they did get a service account credential and queried a production cloud data warehouse. Roughly 12 hours in, they signed in to Microsoft 365 as an integration service account using legacy authentication.
The lesson is the blast radius. A Confluence server holds database credentials and attachments full of secrets, so a code execution bug there becomes a credential theft problem fast.
What to do, in order
- Find Axis 1. Check Java applications and bundled libraries for Axis 1.x, including in vendor products you do not maintain. Ask those vendors whether they ship it.
- Confluence first. If you run Confluence, check whether the Remote API (XML-RPC & SOAP) setting is on. Turn it off if nothing needs it, and plan the move to Confluence 10.0 or later, where the feature is gone.
- Remove or isolate what you cannot replace. Take Axis 1 services off the internet and migrate to a supported SOAP stack. CISA’s guidance for end-of-life products is to discontinue use if mitigations are unavailable.
- Hunt if you were exposed. Review Confluence and server logs since early November for unexpected outbound connections to tunnel services, and rotate the database credentials and service account secrets that Confluence can read.
- Kill legacy authentication on Microsoft 365 integration accounts. It was the path the attackers used for the cloud sign-in.
Priority call
Internet-facing Confluence with the remote API enabled goes to the top of the list. Internal-only Axis 1 services come next. Do not wait for a patch that will not arrive.
Related: see the CVE-2026-90436 record, our Apache hub, and the Apache Roller exploitation report.
- [ CRITICAL ]CVE-2026-90436Apache Axis Unsafe Reflection Vulnerability
Found this useful? Share it.


