FORSMILE
JA
セキュリティ2026/11/20

[Urgent] Apache Axis 1.x CVE-2026-90436: Added to CISA KEV on Nov 18 — Axis Embedded in Confluence Data Center and Others Is Being Attacked; Unauthenticated Code Execution Possible. Confluence Fix Is 9.2.28; No Fixed Axis 1.x Release (CVSS v3.1 9.8)

CVE-2026-90436 in Apache Axis 1.x (through 1.4), a Java SOAP engine, was added to CISA's Known Exploited Vulnerabilities catalog (KEV) on November 18. Rapid7 reports detecting an attack on Atlassian Confluence Data Center on November 13. Apache will not release a fixed Axis 1.x version; for Confluence the vendor points to 9.2.28 or turning off the Remote API, and for N-central to disabling the legacy API and updating. This article covers how to check and what we could not confirm.

← Back to Blog

CVE-2026-90436, in Apache Axis 1.x (a Java engine for SOAP, the XML format systems use to talk to each other), was added to the CISA "KEV" catalog on November 18, 2026. KEV lists vulnerabilities that have been exploited in the wild. According to the Apache Software Foundation, when Axis receives a SOAP Fault, it loads the class named in the message and, if a String is supplied, instantiates it before checking that it is an AxisFault. This happens before any per-service handler runs, so authentication you configured on a service does not protect against it. If a suitable class is on the application's classpath, this can lead to remote code execution.

Even if you never installed Axis yourself, you may not be safe, because other products use it internally. Atlassian says Confluence Data Center uses Axis for its XML-RPC and SOAP APIs and is affected. The security firm Rapid7 reports that on November 13 it detected an attack on Confluence Data Center in a customer environment, and says N-able's remote management software N-central was also attacked in the same way. Apache Axis 1.x itself is end-of-life and Apache does not plan to release a fixed version. So what you should do depends on which product you run. First, check your Confluence Data Center, your N-central, and any Axis 1.x you built in yourself.

⚠ CVE Score — 最高危険度 / CRITICAL
9.8CRITICALCVSS v3.1CVE-2026-90436

Where the score comes from: 9.8 (CVSS v3.1, CRITICAL) is the value NVD lists for CISA-ADP. The vector is network, low complexity, no privileges, no user interaction, unchanged scope, and high impact on confidentiality, integrity and availability. NIST's own assessment was not in the NVD metrics when we checked through the API on November 20. Apache, as the CNA, gives a text severity of "critical" rather than a numeric score. For Confluence Data Center, Atlassian gives its own rating of CVSS v4.0 9.3 (critical). This article uses the CISA-ADP 9.8 listed in NVD.

What is happening (as published)

  • ▸CVE-2026-90436: Apache Axis 1.x loads the class named in the <detail><exceptionName> of an incoming SOAP Fault and, if a String <data> element is present, instantiates it through its String constructor. The check that it is an AxisFault comes afterward. Loading alone runs the class's static initializer. The weakness type is CWE-470 (use of externally controlled input to select classes or code, "unsafe reflection")
  • ▸Why it happens before authentication: Apache says the Fault is parsed while the engine resolves the target service, before any per-service handler chain runs. Authentication handlers configured on a service therefore do not protect against it
  • ▸When it leads to code execution: "with a suitable class on the application's classpath." The fix commit message gives, as an example, Spring's ClassPathXmlApplicationContext (the same kind of gadget as in CVE-2023-46604)
  • ▸Affected versions: Apache Axis 1.x through 1.4 (the NVD CPE range is 1.0 to 1.4). The CVE record lists the Maven packages axis:axis and org.apache.axis:axis
  • ▸Fix for Axis itself: Apache says it does not expect to release a fixed 1.x version and points to migrating to another SOAP engine (for example, Apache Axis 2/Java) or building Axis with the patch from commit 41f3b4e8. The commit makes Axis load the exceptionName class without initializing it and accept only AxisFault subtypes. The commit is dated July 12, 2026
  • ▸Atlassian Confluence Data Center: Atlassian says Confluence Data Center 1.x through 9.x is affected (10.x and later are not, and Atlassian Cloud is not affected). The condition is that the "Remote API (XML-RPC & SOAP)" setting is enabled. That setting has been off by default for new installations since version 3.0, and the feature was removed in 10.0. The fixed version is 9.2.28
  • ▸Observed attack: Rapid7 says that on November 13 it detected, in a customer's Confluence Data Center, unauthenticated POST requests to /plugins/servlet/soap-axis1/confluenceservice-v2 (each returning HTTP 500), followed within seconds by Confluence's Java process launching Bash and curl. Rapid7 says the attacker then used credentials stored in Confluence (such as database credentials and credentials for connected services) to explore the internal environment. Rapid7 also says a Metasploit module for this CVE against Confluence was released on November 17
  • ▸N-able N-central: Rapid7 says some versions of N-central also use Axis, that N-able reported exploitation on November 13, and that a proof-of-concept exploit targeting N-central was published on November 12. N-able tells on-premises administrators to confirm that the "Legacy API" is disabled, and its 2026.4 HF3 (build 2026.4.1.39, November 16) removed the legacy API setting and blocks legacy APIs permanently. The N-able pages we read do not name the CVE number (Rapid7 says the N-central attack "strongly correlates" with CVE-2026-90436)
  • ▸Timeline and KEV entry: the CVE was published on November 6, 2026 and added to KEV on November 18. The due date for U.S. federal agencies is November 21, known ransomware campaign use is "Unknown," and forensic triage is marked "Yes." The finder is credited as José Apari-Pantigozo of OKIOK

What to do today (check your own environment)

  • ✓★Step 1: If you run Confluence Data Center, check the "Remote API (XML-RPC & SOAP)" setting. In General Configuration, under Further Configuration, clear the "Remote API (XML-RPC & SOAP)" checkbox and save (no restart is needed). To verify, Atlassian says to browse to /plugins/servlet/soap-axis1/confluenceservice-v2 and confirm you get "HTTP Status 403 - Forbidden." Turning it off may stop scripts, automations and third-party add-ons (Atlassian)
  • ✓★Step 2: Update Confluence Data Center to 9.2.28, or to an unaffected 10.x or later. Atlassian recommends the latest version or the fixed version it lists. Environments where this setting is still enabled should hurry
  • ✓★Step 3: If you run on-premises N-central, confirm that the "Legacy API" is disabled and update to 2026.4 HF3 (2026.4.1.39). N-able tells both hosted and on-premises customers to update their Agents and Probes to the latest version
  • ✓★Step 4: If you have your own Axis 1.x, migrate to another SOAP engine or use a build with the patch Apache points to. In your Java applications and the folders that hold their libraries, look for files such as axis-1.x.jar and classes under org.apache.axis. In your build tool, look for org.apache.axis:axis and axis:axis. Close any SOAP endpoint that does not need to be public (our addition). Apache says authentication settings do not protect against this
  • ✓Step 5: Look for signs of exploitation. In the case Rapid7 observed, unauthenticated POST requests reached /plugins/servlet/soap-axis1/confluenceservice-v2 (HTTP 500), and Confluence's Java process then launched Bash and curl. Check the access logs and the server's process records for the same pattern. Rapid7 and N-able publish lists of IP addresses and other indicators tied to the attacks. Rapid7 notes that not matching the list does not mean you are unaffected
  • ✓Step 6: If you find signs, rotate the credentials stored on that server. (our addition) In the intrusion Rapid7 reported, database and connected-service credentials stored in Confluence were used for the next steps. Consider replacing passwords, keys and tokens kept on the server
  • ✓Step 7: If you do not know whether you use it, ask the vendor or the team that built the system. Axis 1.x can run inside delivered systems or products you did not build yourself

What we could not confirm

  • ▸The overall picture of the attacks. We confirmed the case Rapid7 observed and the attacks N-able reported. The sources we could read do not give the number of attacks, who is behind them, or how many organizations were targeted
  • ▸Whether N-able's own pages name CVE-2026-90436. We could not find the CVE number on the two N-able pages we read (the HF3 release notes and the November 13 update). The link between N-central and this CVE comes from Rapid7's explanation
  • ▸Products other than Confluence and N-central that bundle Axis 1.x. The sources we could read do not tell us whether other products are affected. The KEV description says the component can be used by different products
  • ▸NIST's assessment. On November 20, NVD showed no NIST assessment of its own. The 9.8 is CISA-ADP's. Apache (the CNA) rates it with the text "critical," not a number
  • ▸Whether the calling side (the client) is affected. Apache describes a path on the side that receives requests, where the Fault is parsed while the target service is resolved. The sources we could read do not describe what happens on the calling side
  • ▸Whether a self-built patched version affects other behavior. The sources we read do not say. Test before replacing

Three lines to share

  • ▸CVE-2026-90436 in the old SOAP software Apache Axis 1.x was added to CISA's "known exploited" catalog (KEV) on November 18. Rapid7 observed an attack on Confluence Data Center (with the Remote API enabled) on November 13. Code can be run without authentication
  • ▸★For Confluence Data Center, update to 9.2.28 or turn off "Remote API (XML-RPC & SOAP)." For N-central, disable the "Legacy API" and update to 2026.4 HF3. There is no fixed Axis 1.x release
  • ▸Check whether Confluence, N-central or Axis 1.x is in your systems or in those run by your contractors. If you find signs of an attack, rotate the credentials stored on that server

Pages this article is based on

参考リンク / References
Related articles
[Urgent] LiteLLM CVE-2026-40217: Added to CISA KEV (Nov 18) — The Guardrail Test API Sandbox Can Be Escaped to Run Code on the Proxy; Update to 1.83.11 or Later (CVSS v3.1 8.8)2026/11/19[Urgent] UnrealIRCd CVE-2026-114713: Added to CISA KEV on Nov 13 — On IRC Networks With Two or More Linked Servers, Any User May Run Commands With Server Authority; Fixed in 6.2.7.1 or With a Hot-Patch (CVSS v3.1 7.7)2026/11/17[Urgent] Check Point Gaia CVE-2026-123039: Added to CISA KEV on Nov 13 — Check Point Confirmed Attacks That Take root via DynamicCLI After Breaking In Through the Mobile Access Portal; Fixed in the November Jumbo Hotfix (R82.20 Take 14 and Later, and More) (CVSS v3.1 7.8)2026/11/16[Urgent] Microsoft Outlook CVE-2026-124194: Added to CISA KEV on Nov 10 — Opening a Crafted Message File May Hand an Attacker Your Windows Login Hash (NTLMv2); Fixed in the Nov 10 Office Update (CVSS v3.1 6.5)2026/11/13[Urgent] Google Chrome (Chromium) CVE-2026-125350: Added to CISA KEV on Nov 10 — Use-After-Free in XML Handling May Let a Crafted Web Page Run Code Inside the Sandbox; Chrome 157.0.8103.50 and Later (Extended Stable 156.0.8078.96 and Later) Are the Fixed Releases (CVSS v3.1 8.8)2026/11/12