For: IT, development and platform teams running Java business systems, internal tools, Atlassian products or MSP management tools that may contain Apache Axis 1.x. This article is based on Apache's announcement, Atlassian's advisory and CISA KEV; it does not cover attack steps.
続報待ち:この記事は公式発表に合わせて更新します
- Who is affected
IT, development and platform teams running Java business systems, internal tools, Atlassian products or MSP management tools that may contain Apache Axis 1.x.
- Confirmed so farSee the table ↓
- The flaw
- Affected and remedy
- Confluence Data Center
1 more
- Exploitation against Confluence
- Not yet confirmed
- Whether N-central exploitation is this CVE, per N-able's official page (we could not retrieve it and treat it as the security firm's report)
- Whether other flaws were chained (not stated in CISA KEV, Apache or Atlassian materials)
- Other products that bundle Axis 1.x and their vendors' fixes
- What to do nowSee the steps ↓
- Find where Axis 1.x is installed
- Confluence Data Center: 9.2.28 or later, or disable the API
- If you run N-central, follow N-able's guidance
2 more
- Your own applications: migrate or use the patched build
- Look for signs of compromise
- Where to verify (source)All sources ↓
- Apache Axis
- Last checked
- as of November 19, 2026
Follow-up plans and what we checked
CISA added the flaw to KEV on November 18. Atlassian's advisory does not mention confirmed exploitation; exploitation against Confluence is a security firm's report (the security firm's article in the sources). Press reports say it was exploited together with other flaws, but CISA, Apache and Atlassian materials do not say so, and this site could not confirm it.
What to do today
Find where Axis 1.x is installed
Search servers, application bundles and product install directories for files named axis-1.x.jar (through 1.4); in Maven, axis:axis or org.apache.axis:axis. Use your software bill of materials (SBOM) if you have one. Old SOAP systems tend to be left without updates (a general observation), so include dormant internal systems (asset inventory checklist).
Confluence Data Center: 9.2.28 or later, or disable the API
Per Atlassian's advisory, Confluence Data Center 1.x through 9.x is vulnerable when "Remote API (XML-RPC & SOAP)" is enabled (this setting has been off by default for new installations since 3.0 and the feature was removed in 10.0), 9.2.28 is the fix, 10.x and later are not affected, and Atlassian Cloud is not affected. Until you can update, disable "Remote API (XML-RPC & SOAP)" under Further Configuration (no restart; scripts and add-ons that use the API will stop working, so test first). The advisory says you can verify by browsing to /plugins/servlet/soap-axis1/confluenceservice-v2, which should return 403.
If you run N-central, follow N-able's guidance
Per the security firm's report, on-premises N-central is affected when the Legacy API is enabled, and the fix is 2026.4 HF3 (2026.4.1.39), which disables the Legacy API. We could not retrieve N-able's official page, so confirm versions and steps in N-able's own guidance (our N-central article).
Your own applications: migrate or use the patched build
Apache recommends moving to another SOAP engine such as Axis 2/Java, or using a build with the patch from the published commit (41f3b4e8d04e). Migration takes time, so in the meantime keep SOAP endpoints off the internet (behind a VPN or allowlist) to cut the entry points.
Look for signs of compromise
The same firm reports that, in the attacks it observed, the logs showed unauthenticated requests to SOAP/Axis endpoints and the Confluence Java process launched unexpected child processes. Check web server and application logs for such requests, and look for unexpected child processes of the Java process running as the Confluence service account. No match does not prove you are clean. If anything looks wrong, isolate the server and rotate the credentials it stores (how to check for intrusion).
What kind of flaw this is
- CVE
- CVE-2026-90436 (Apache Axis 1.x: unauthenticated class instantiation via SOAP fault exceptionName)
- Severity
- CVSS v3.1 9.8 (critical; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; CISA container score)
- Type
- Use of externally-controlled input to select classes or code (unsafe reflection, CWE-470)
- Impact
- With a suitable class on the classpath, unauthenticated remote code execution
- Affected
- All Apache Axis 1.x through 1.4; EOL
- Fix
- No Axis 1.x fix release. Migrate to another SOAP engine, or use a build with the published patch (commit 41f3b4e8d04e) (Apache)
- Published
- Apache announcement and CVE published November 6, 2026. Atlassian advisory November 9 (last modified the 10th)
- Exploitation
- Added to CISA KEV November 18 (due November 21). Ransomware use Unknown, Forensic Triage Yes
- In short: when Axis reads a received SOAP error response, it loads the class named in it and instantiates it with a supplied string. Merely loading a class runs that class's initializer. This happens before any per-service authentication (Apache's announcement). Request details are not included.
- Whether it becomes code execution depends on a suitable class on the application's classpath (Apache), so risk differs between environments running the same Axis 1.x. That is not grounds to call any environment safe.
- It was found by a researcher at a security firm (credit in Apache's announcement).
- The KEV note says it may affect an open-source component or library used by different products.
What is known and what is not
| Item | Content | Status |
|---|---|---|
| The flaw | Class instantiation via SOAP fault (Apache) | Confirmed (Apache) |
| Affected and remedy | Axis 1.x through 1.4; no fix release, migrate or use patched build | Confirmed (Apache) |
| Confluence Data Center | 1.x through 9.x affected, 9.2.28 fixed, 10.x and Cloud not affected | Confirmed (Atlassian) |
| Exploitation against Confluence | In KEV. A security firm reports detecting exploitation in a customer environment on November 13. Atlassian's advisory does not mention it | Exploitation confirmed (CISA; the security firm's report) |
| Exploitation against N-central | The firm says N-able reported exploitation on November 13 and that it "strongly correlates" with this CVE | Under investigation (N-able's official page not confirmed by us) |
| Chaining with other flaws | Not in CISA, Apache or Atlassian materials | Not stated |
Sources
- Apache Axis — CVE-2026-90436 announcement (java-user mailing list, November 6, 2026) (affected versions, remedy, credit)
- Atlassian — CVE-2026-90436 - Remote Code Execution in Confluence Data Center (November 9; affected versions, fixed version, workaround)
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 18, due November 21)
- CVE.org — CVE-2026-90436 (published November 6, 2026)
- NVD — CVE-2026-90436
- Rapid7 — Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited (security firm report: exploitation detection, N-central fix; cross-checked with primary sources)
Attack steps and indicators of compromise (IOCs) are not included. Last verified: November 19, 2026.
Update history
2026-11-19: First report. Based on Apache's announcement, Atlassian's advisory and CISA KEV; exploitation against Confluence and N-central is recorded separately as a security firm's report.
Read next
- Related: N-able N-central vulnerabilities suspected exploited (November 2026)
- The pattern: What insecure deserialization is
- Practice: Vulnerability remediation playbook / Asset inventory checklist
- Prioritizing: Deciding fix order with CVSS, EPSS and KEV
- Term: What RCE (remote code execution) is