Apache Axis Bug (CVE-2026-90436) Added to CISA's Exploited List

CVE-2026-90436, a critical flaw in the end-of-life Apache Axis 1.x library, is now on CISA's exploited list after Rapid7 traced live attacks through Confluence Data Center and N-able N-central.

CISA has added CVE-2026-90436, a critical unsafe-reflection flaw in the end-of-life Apache Axis 1.x library, to its Known Exploited Vulnerabilities (KEV) catalog. The flaw lets an unauthenticated attacker force a vulnerable server to instantiate an arbitrary Java class by sending a crafted SOAP fault message — and Rapid7 says it has already seen it used against both Atlassian Confluence Data Center and N-able's N-central remote monitoring platform.

Key facts
  • CVE-2026-90436 was disclosed to the oss-security mailing list on November 6, 2026, by the Apache Axis project.
  • CVSS 3.1 score: 9.8 (critical); it requires no authentication and no user interaction.
  • CISA added it to the KEV catalog on November 18, 2026, with a remediation due date of November 21.
  • Apache Axis 1.x is end-of-life and will not receive an official fix — the project recommends migrating off it.
  • Confirmed exploitation: Atlassian Confluence Data Center (Rapid7, Nov. 13) and N-able N-central.

What is CVE-2026-90436?

Apache Axis is an old Java framework for building and consuming SOAP web services, largely superseded in current software by Axis2 and other frameworks — but still quietly embedded inside plenty of enterprise products that added SOAP/XML-RPC support years ago and never removed it. According to the disclosure posted to the oss-security mailing list by the Apache Axis project on November 6, 2026, the flaw lives in how Axis 1.x parses an inbound SOAP fault message. When a fault includes a <detail><exceptionName> element, Axis loads the Java class named inside it. If the fault also carries a string <data> element, Axis goes a step further and instantiates that class through its string constructor — before ever checking whether the class is actually a legitimate AxisFault type.

Because simply loading a class runs its static initializer, and the fault gets parsed while Axis is still resolving which service to route the request to, the bug triggers before any service-level authentication handler has a chance to run. In practice, that means turning on authentication for the SOAP service sitting behind Axis does not protect against this particular flaw — the vulnerable code path runs first.

Severity: a 9.8 with no authentication required

DetailValue
CVE IDCVE-2026-90436
CVSS 3.1 score9.8 (Critical)
VectorAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness typeCWE-470 (unsafe reflection)
AffectedApache Axis 1.x, all versions through 1.4 (end-of-life)
Fix available?No official Axis 1.x patch; migrate to Axis2 or apply a community patch manually

A 9.8 score sits near the top of the CVSS scale, reflecting that the bug needs no credentials, no user interaction, and can fully compromise confidentiality, integrity, and availability of the affected system. The finder is credited as José Apari-Pantigozo of the security firm OKIOK, with the disclosure itself posted by Apache contributor Robert Lazarski.

Why there's no official patch coming

Apache Axis 1.x has been end-of-life for years, and the project's own disclosure says plainly that it does not expect to release a fix for the 1.x branch at all. Its stated guidance is to migrate to a different, maintained SOAP engine — Axis2/Java is the example it names — rather than wait for a patch that isn't coming. For organizations that can't migrate on short notice, the advisory offers a fallback: the fix is already written and sitting in a specific commit (identified by the project as the range ending at commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd), so a team with the engineering resources to maintain a local fork can backport that change themselves. That's a meaningfully higher bar than installing a vendor patch, which is part of why this flaw has turned into a bigger story than its single CVE number suggests — it isn't really one bug to fix, it's an unmaintained dependency to find and replace across however many products embedded it.

Why "Apache Axis" doesn't mean just one thing

Confusingly, "Apache Axis" refers to two separate, largely unrelated code bases that happen to share a name and a general purpose. Axis 1.x, the version affected here, was Apache's original Java SOAP engine, first released in the early 2000s and effectively frozen in its current end-of-life state for years. Axis2, sometimes written Axis2/Java, is a later, architecturally different rewrite that remains under at least nominal maintenance and is not affected by this specific flaw. The practical confusion this causes: a developer or administrator searching their own systems for "Apache Axis" to check their exposure may find references to Axis2 and incorrectly assume they're covered, when the vulnerable code is specifically the older 1.x branch. Checking a dependency's exact version string, not just its project name, is the only reliable way to confirm which one you're running.

How it's being exploited: Confluence Data Center

Atlassian Confluence Data Center bundles Apache Axis 1.x to power its legacy XML-RPC and SOAP remote API. Security firm Rapid7 reported that its managed detection team observed exploitation of CVE-2026-90436 against a Confluence Data Center customer on November 13, 2026. Atlassian's own tracking ticket for the issue, CONFSERVER-104610, confirms the Axis dependency as the root cause and lists Confluence Data Center 9.2.28 as the fixed version. Critically, the vulnerable remote API is only reachable at all if an administrator has specifically enabled Confluence's "Remote API (XML-RPC & SOAP)" setting — it's disabled by default on current installs, which narrows the exposed population to servers where that legacy integration was turned on, often years ago, and never turned back off.

How it's being exploited: N-able N-central

N-able's N-central, a remote monitoring and management platform widely used by managed service providers to administer client networks, is the second confirmed target. Because N-central instances typically sit at the center of an MSP's access to dozens or hundreds of downstream client networks, a successful compromise here carries outsized risk compared to a single-organization Confluence server — it's the kind of single point of failure that ransomware operators specifically look for when picking a target with maximum downstream reach. A public proof-of-concept exploit targeting N-central began circulating on November 12, a day before Rapid7's reported Confluence detection, which likely accelerated exploitation attempts across both products. Reporting on the N-central exploitation is less precise than Rapid7's Confluence finding: some sources describe the activity as a vulnerability that "strongly correlates" with CVE-2026-90436 rather than a confirmed one-to-one match, which is common in the early days of a disclosure when multiple security vendors are independently tracking overlapping attack telemetry before a single, agreed-upon attribution settles out. Either way, N-able has acknowledged active exploitation against N-central and the practical remediation advice is unaffected by that nuance: patch now rather than wait for perfect attribution.

Who else might be quietly running Axis 1.x

Confluence and N-central are the two products with confirmed exploitation, but neither is likely to be the only software bundling the vulnerable library. Apache Axis 1.x was popular enough in the 2000s and early 2010s that it ended up embedded inside a wide range of enterprise middleware, internal integration tools, and legacy line-of-business applications that added SOAP web service support during that era and have had little reason to revisit that dependency since. Security researchers commonly describe this category of risk as "vendored" or "shaded" dependencies — code bundled directly inside another product's installer rather than tracked as an external library — which is precisely why a flaw like this one can stay hidden from routine vulnerability scanning until someone specifically goes looking for it, or until attackers find it first.

What CISA's KEV listing actually requires

CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalog on November 18, 2026, with a remediation due date of November 21. The KEV catalog only exists to track vulnerabilities CISA has confirmed are being actively exploited, so a listing itself is a signal independent of the CVSS score — it means real attacks, not theoretical risk. CISA's required action is to apply vendor mitigations in line with its Binding Operational Directive 26-04, or discontinue use of the affected product if no mitigation exists; for an unauthenticated, unpatched, EOL library embedded inside other software, "apply vendor mitigations" in practice means patching whichever downstream product (Confluence, N-central, or anything else) bundles the vulnerable Axis code, since there's no way to patch Axis 1.x directly.

How to find out if you're exposed

The hard part of this vulnerability isn't patching it — it's discovering it, because Apache Axis 1.x is a dependency buried inside other software rather than something IT teams install and track directly. If you run Confluence Data Center, check whether the Remote API (XML-RPC & SOAP) setting is enabled under your general configuration, and upgrade to 9.2.28 or later regardless of whether that setting is on, since a setting someone enabled years ago for an integration nobody remembers can be easy to miss during an audit. If you run N-central, apply N-able's current patches and review recent authentication logs for anomalous activity predating the public proof-of-concept's November 12 release. More broadly, any product in your environment that offers (or once offered) SOAP or XML-RPC API support is worth a quick check against its vendor's own security advisories for an Axis 1.x dependency, since Confluence and N-central are simply the two targets confirmed exploited so far, not necessarily the only ones affected. Rapid7 and other security research teams, including Rapid7's own threat research blog, are a reasonable place to watch for additional confirmed targets as the disclosure continues to circulate; expect that list to grow over the following weeks rather than staying fixed at two products.

How this fits the pattern of other recent KEV additions

CVE-2026-90436 joins a run of other fresh CISA KEV additions this month, including flaws in widely deployed consumer and enterprise network gear. What sets this one apart is that the vulnerable code isn't a product in its own right that a vendor can simply patch and push — it's an abandoned dependency quietly inherited by whichever products built on top of it years ago, which is exactly the kind of software supply chain risk that security teams have struggled to inventory. Expect more products to surface an Axis 1.x connection to this CVE in the coming weeks as vendors audit their own dependency trees following the public disclosure.

What's next

Federal civilian agencies face a November 21 deadline to remediate under CISA's directive, but the practical advice applies to any organization: inventory where Apache Axis 1.x might be hiding, patch the downstream products that have already shipped fixes (Confluence Data Center 9.2.28 among them), and treat any server exposing a legacy SOAP or XML-RPC endpoint as a priority for review even if it isn't Confluence or N-central specifically. With no upstream fix ever coming for Axis 1.x itself, the long-term fix for affected organizations is migration, not patching. It's also a reminder to revisit any legacy integration still running on infrastructure originally secured against older threats, in the same way the recent Java4Shell flaw in OpenJDK pushed Java shops to re-audit code they hadn't touched in years.

Frequently asked questions

What is CVE-2026-90436?

A critical unsafe-reflection vulnerability (CWE-470) in the end-of-life Apache Axis 1.x SOAP engine that allows unauthenticated remote code execution via a crafted SOAP fault message.

Is there an official patch for Apache Axis 1.x?

No. The Apache Axis project says it does not expect to release a fix for the 1.x branch and recommends migrating to Axis2 or applying the fix commit manually.

Which products are confirmed to have been exploited?

Atlassian Confluence Data Center and N-able's N-central have both seen confirmed or strongly correlated exploitation tied to this flaw.

How do I fix Confluence Data Center against this flaw?

Upgrade to Confluence Data Center 9.2.28 or later, and check whether the Remote API (XML-RPC & SOAP) setting is enabled in your configuration.

Why did CISA add this to its KEV catalog?

The KEV catalog only lists vulnerabilities CISA has confirmed are being actively exploited, which it did for CVE-2026-90436 on November 18, 2026, with a November 21 remediation deadline for federal agencies.

Sources

More on Apache Axis →Apache AxisCISA KEVConfluenceN-ableCVE-2026-90436vulnerability
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all