Security advisory · Apache Axis · Confluence

Unsafe reflection in Apache Axis reaches Confluence Data Center

CVE-2026-90436 is an unsafe-reflection flaw in the end-of-life Apache Axis 1.x SOAP library that can lead to unauthenticated remote code execution. It is reached through products that bundle Axis, with Atlassian Confluence Data Center confirmed and N-able N-central correlated. It is in the CISA Known Exploited Vulnerabilities catalog.

01 At a glance

What is affected

The flaw, CWE-470 (unsafe reflection), is in Apache Axis 1.x, an end-of-life SOAP engine for Java. A crafted SOAP fault names a class; Axis loads and instantiates it before confirming it is a valid fault, and simply loading a class runs its static initializer. With a suitable class on the classpath, that can lead to remote code execution. Because the fault is handled before a service’s own handlers, authentication configured on the service does not protect it.

The flaw affects products that bundle Axis 1.x. Two are in focus here: Atlassian Confluence Data Center, which uses Axis for its XML-RPC and SOAP APIs, and N-able N-central, which Rapid7 correlates with this CVE. N-able has not confirmed it as the same CVE.

02 Severity by issuer

Severity, quoted with its issuer

Issuers scored this on different scales. Each rating is quoted with the organization that assigned it.

Severity, quoted with its issuer
IssuerRating
Apache (CNA)Labelled “critical” (the project’s own label, no CVSS score)
CISA ADP (Vulnrichment)CVSS 3.1 9.8 (critical)
AtlassianCritical; CVSS 4.0 9.3 (its internal assessment)
NVDNo score yet (undergoing analysis)
03 Affected and fixed

Affected and fixed versions

The library has no fixed release; remediation differs by product.

Affected and fixed versions
ProductAffectedFixed in
Apache Axis (library)1.x through 1.4No fixed release; migrate to Axis 2, or apply the project’s patch
Confluence Data Center1.x through 9.x9.2.28 (10.x and later are not affected)
N-able N-centralNot stated by N-able for this CVE2026.4 HF3 blocks the legacy APIs
04 Precondition

A non-default setting has to be on

Neither affected product is exposed by default. Confluence is only vulnerable if the “Remote API (XML-RPC & SOAP)” option is enabled; it has been off by default since Confluence 3.0, but an instance upgraded from an old version, or one that turned it on, may still have it enabled. N-central needs its Legacy API enabled, which is also off by default. Neither condition is visible from outside with ordinary traffic, which is why an external check can only produce a signal to validate, not a confirmation.

05 Exploitation status

What is known about exploitation

The CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog, added on 18 November 2026 with a due date of 21 November 2026, and CISA’s SSVC assessment that day recorded exploitation as active, automatable, with total technical impact. For Confluence, Rapid7 reports that its managed detection service saw exploitation in a client environment on 13 November 2026; Atlassian’s own advisory does not claim exploitation, saying only that it “cannot confirm” whether instances were affected and advising a check for compromise. For N-central, N-able reports indicators of compromise found during its investigation but does not tie them to this CVE; that link is Rapid7’s.

06 Check yourself

How to check your exposure from outside

Run these checks only on systems you own or are authorized to test.

  1. Read the Confluence version

    A Confluence page you already load may expose its version in markers such as ajs-version-number, in the footer line “Powered by Atlassian Confluence x.y.z”, or in build information.

  2. Treat the version as a signal

    The precondition, the Remote API being enabled, is not visible without calling the API endpoint, which we do not do. A version in the affected range needs validation.

  3. N-central has no outside check

    N-able published no affected-version range for this CVE, and the normal interface does not reliably expose a version, so there is no dependable external check for N-central.

  4. Confirm the configuration inside

    The reliable check is in the product: whether the Remote API (Confluence) or the Legacy API (N-central) is turned on.

07 What to do

How to fix it

  • Confluence: update to 9.2.28 or later; 10.x and later are not affected. If you cannot update now, an administrator can disable “Remote API (XML-RPC & SOAP)” in General Configuration, with no restart needed. Atlassian warns this can break scripts, automations and add-ons, so test it first, and check for signs of compromise.
  • N-central: make sure the Legacy API is disabled, and update to 2026.4 HF3 (build 2026.4.1.39), which blocks the legacy APIs permanently.
  • Apache Axis in other products: migrate to Axis 2, or apply the project’s patch. CISA advises applying mitigations or discontinuing use.
08 Our view

How NorthBound looks at this

As part of tech stack intelligence, we recognize products like Confluence and match their versions to new CVEs with CISA KEV context. Because the condition that makes this flaw exploitable is a setting we cannot see from outside, a version match is a signal to validate, not a confirmed finding, and we label it that way. Our team reviews each match; we do not call the SOAP or XML-RPC endpoints and we do not attempt exploitation.

Find it before an attacker does.

Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.

Facts on this page verified 11 November 2026.