On November 18, 2026, CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalog and set a due date of November 21, 2026 for federal agencies under BOD 26-04. The flaw is an unsafe reflection weakness (CWE-470) in end-of-life Apache Axis 1.x SOAP libraries that can enable unauthenticated remote code execution when a suitable class is on the application classpath.
This is a national cyber-alert for small businesses that run Atlassian Confluence Data Center on-prem or that rely on an MSP using N-able N-central. It is not a Texas-only breach notice. It pairs with the separate Java4Shell JVM issue — see Java4Shell CVE-2026-114938 — but CVE-2026-90436 is a bundled Axis 1.x problem in products that still expose legacy SOAP/XML-RPC endpoints, not the HotSpot Base64 decoder path.
Law firms that host matter wikis or client collaboration on Confluence Data Center, or that rely on an MSP using N-central, should treat this as a patch-and-questionnaire week even when they never log into the server console.
Apache disclosed the vulnerability on November 6, 2026. Rapid7 (published November 16, 2026, updated November 19, 2026) cites CISA’s CVSS 3.1 score of 9.8 Critical, reports active exploitation against Confluence Data Center, and says N-able reported exploitation in the wild against N-central for a vulnerability that strongly correlates with CVE-2026-90436 when non-default API settings remain enabled.

Snapshot
| Field | Detail |
|---|---|
| CVE | CVE-2026-90436 (Apache Axis 1.x unsafe reflection) |
| Apache disclosure | November 6, 2026 |
| CISA KEV | Added November 18, 2026 · Federal agency due date November 21, 2026 |
| CVSS (CISA) | 9.8 Critical (Rapid7) |
| Axis status | Axis 1.x through 1.4 affected; EOL — “does not expect to create an Axis 1.x release” (Apache Axis, Nov 6) |
| Confluence DC | 1.x–9.x when Remote API (XML-RPC & SOAP) is on · fixed 9.2.28 (Atlassian) · 10.x+ removed feature · Cloud unaffected |
| N-central | Legacy API exposed Axis surface; 2026.4 HF3 (build 2026.4.1.39) disables it (Rapid7) |
| Exploitation | Rapid7 MDR November 13, 2026 on Confluence; N-able November 13 in-the-wild report strongly correlates with this CVE (Rapid7) |
Why small businesses should care
Many firms never open Confluence or N-central themselves. If your managed service provider runs N-central, a flaw on their platform can become your outage, credential hunt, or Microsoft 365 session — without a phishing email to the owner.
Rapid7’s incident write-up describes unauthenticated POST requests to /plugins/servlet/soap-axis1/confluenceservice-v2 on Confluence Data Center. Even when responses were HTTP 500, endpoint telemetry showed the Confluence Java process spawning bash and curl as the dedicated service account. The actor ran hundreds of hex-encoded commands, pulled scripts from Pinggy and trycloudflare.com tunnels, and mined Confluence attachments and database content for credentials and VPN material.
Roughly four hours after the first exploit request, Rapid7 says the actor used a service account credential to query a production cloud data warehouse. About twelve hours after the first request, the attacker signed in to Microsoft 365 as an integration service account using legacy authentication from 192.238.253[.]176 — an address Rapid7 also ties to earlier exploit traffic.
SecurityWeek (November 19, 2026) summarizes vendor and researcher reporting and notes Previdian sensor data showing 50 exploitation attempts from 14 IP addresses between November 12 and 19 — without establishing success rates.

Apache Axis 1.x will not be patched upstream
The Apache Axis disclosure (November 6, 2026) states that Apache Axis 1.x through 1.4 is end of life and that “The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.” It recommends migrating to another SOAP engine (for example Apache Axis 2) or using an Axis 1.x build with Apache’s published patch applied.
We do not recommend downloading and swapping a standalone Axis 1.x tarball on production app servers unless your vendor explicitly documents that path. Remediation is product-specific: patching only a generic Java runtime does not close an embedded Axis servlet still mapped on the network.
Sibling flaw: Apache Roller (not in KEV)
Apache’s oss-security advisory (November 17, 2026) confirms active exploitation of CVE-2026-129448 in Apache Roller (CVSS 9.8). Affected releases are 4.0.0 through 6.1.4, plus 6.1.5 under the earlier CVE-2026-82384 identifier. Fixed builds start at 6.1.6; 6.1.7 rolls up additional fixes (SecurityWeek). Disabling XML-RPC in the Roller administration UI does not stop exploitation on vulnerable versions — deserialization runs before that check (oss-security, Nov 17). Interim mitigations per Apache: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller.
As of CISA KEV catalog version November 18, 2026, CVE-2026-129448 is not listed — unlike CVE-2026-90436. If you still host Roller blogs, patch on the Roller advisory; this post focuses on Confluence and N-central because those are the paths most SMBs touch through collaboration tools and MSP stacks.
Confluence Data Center: patch or kill the Remote API
Atlassian’s advisory (November 9, 2026) rates the issue critical and lists Confluence Data Center 9.2.28 as the fixed 9.x line (release notes, November 10, 2026). Confluence 10.x+ removed the SOAP feature; Atlassian Cloud is not affected.
Vulnerable configuration: Remote API (XML-RPC & SOAP) enabled. Atlassian says that setting has been off by default for new installs since Confluence 3.0, but long-lived servers may still have it on for scripts or integrations.
If you cannot patch immediately
Atlassian documents a configuration mitigation (no restart required):
- General Configuration → Further Configuration → Edit
- Clear Remote API (XML-RPC & SOAP) → Save
- Validate: browse to
<base_url>/plugins/servlet/soap-axis1/confluenceservice-v2and expect HTTP 403 Forbidden (advisory)
Warning: Atlassian notes that turning off Remote API (XML-RPC & SOAP) can break scripts, automations, and third-party add-ons — test in a non-production instance before you apply it firm-wide (advisory).
Rapid7 (published November 16, 2026, updated November 19, 2026) notes a Metasploit module (November 17, 2026) targeting Confluence when that API stays enabled.
N-central: emergency HF3 for MSPs and their clients
Rapid7 documents N-central 2026.4 HF3 (build 2026.4.1.39) as the release that disables the Legacy API surface tied to CVE-2026-90436. N-able’s remediation blog (updated November 16, 2026) lists HF3 and seventeen additional CVE fixes (CVE-2026-129271 through CVE-2026-129287).
HF3 permanently removes Legacy API access — the path SecurityWeek (November 17, 2026) ties to 4EverAble2Shell chains that combine CVE-2026-90436 with an N-central bug when Legacy API stayed on. SecurityWeek reports attackers used the public 4EverAble2Shell proof-of-concept hours after disclosure to deploy cryptocurrency miners on vulnerable servers.
On-premises administrators should upgrade servers to HF3, confirm build 2026.4.1.39, and upgrade Agents and Probes to the vendor’s 2026.4 HF3 component builds. N-able, quoted by SecurityWeek (November 17, 2026), says Agents and Probes that are not upgraded remain susceptible to impersonation.
Known issues at HF3: non–Take-Control remote control remains unavailable; Intune integration remains blocked — N-able states “The Intune integration is currently blocked” (N-able update, Nov 16, 2026).
Questions to ask your MSP (this week)
| Ask | Why it matters |
|---|---|
| Do we run Confluence Data Center (not Cloud)? | Cloud is out of scope for this CVE per Atlassian |
| Is Remote API (XML-RPC & SOAP) enabled on any Confluence instance? | Required for this Confluence attack surface |
| What Confluence build are we on? Will you deploy 9.2.28+ or 10.x? | Vendor fixed path |
| Do you manage us through N-able N-central? What server, Agent, and Probe builds? | HF3 is the emergency server fix |
| Was Legacy API ever enabled in our tenant history? | N-able correlates exploitation with Legacy API |
| After patching, will you run forensics on internet-facing Confluence/N-central? | CISA KEV entry flags forensic triage; Rapid7 lists IOCs |
| Which M365 integration accounts can sign in with legacy auth? | Rapid7 saw M365 access ~12 hours post-exploit |
Watch your own domain’s SPF/DMARC and certificates weekly: Domain Watch ($29/mo). Broader monitoring: services.
Service-account and M365 checklist
| Step | Action |
|---|---|
| 1 | Inventory Confluence and N-central internet exposure; restrict management interfaces to VPN or allow-lists where possible |
| 2 | Treat November 21, 2026 as the federal agency KEV deadline; Rapid7 recommends emergency patching outside normal cycles — use that urgency for your own internet-facing Confluence and MSP stacks |
| 3 | Rotate Confluence database, Crowd, and integration secrets stored in wiki pages or attachments |
| 4 | Hunt for bash/curl children of Java on Confluence hosts and POSTs to soap-axis1 paths in access logs |
| 5 | In Entra ID, block legacy authentication for every integration / automation account |
| 6 | Require Conditional Access + phishing-resistant MFA on admins and on any account that survived a service principal or legacy session review |
| 7 | Review OAuth app consents and N-central → customer tooling after MSP platform incidents |

MFA after the host is already owned
MFA on human logins does not patch Axis. It still matters once attackers pivot from Confluence secrets to Microsoft 365 with a service account that may bypass interactive MFA.
| Grade | Meaning |
|---|---|
| Strong | FIDO2 / YubiKey-class key and open TOTP documented |
| Pass | TOTP or FIDO2 documented; weaker SMS/email paths may remain |
| Fail | No documented YubiKey-class or open TOTP on the login reviewed |
| Platform | Grade | YubiKey | Authenticator |
|---|---|---|---|
| Microsoft Entra ID (workforce) | Strong | Yes — security keys | Yes — Microsoft Authenticator / TOTP |
| Atlassian Cloud account (not DC local login) | Strong | Yes | Yes — Atlassian two-step verification |
| N-central (MSP console) | Pass | Not documented on N-central 2FA guide reviewed | Yes — Google / Microsoft Authenticator named |
Critical distinction: If an M365 service account still allows legacy IMAP/SMTP or basic auth, Conditional Access MFA may never run — consistent with Rapid7’s account-use narrative. Fix auth policy on automation accounts, not only user phones.
Directory: MFA support directory.
Recommended MFA tools
| Product | Best for | Get it |
|---|---|---|
| YubiKey 5C NFC | USB-C laptops + NFC phones | Amazon |
| YubiKey 5 NFC | USB-A desktops + NFC phones | Amazon |
| Proton Pass | Passkeys + authenticator-style TOTP | Proton Pass |
We may earn a commission if you buy a YubiKey or sign up for Proton Pass through the links above.

Independent cybersecurity audits
November 19, 2026 admin domain audit scores appear below (100% is the ideal). Scores reflect email / transport / website posture on vendor marketing domains, not whether your on-prem Confluence build is patched.
| Organization | Domain | Overall | vs 100% |
|---|---|---|---|
| N-able | n-able.com | 86% | −14 |
| Atlassian | atlassian.com | 73% | −27 |
| Domain | Identity | Transport | Website |
|---|---|---|---|
| n-able.com | 85% | 45% | 92% |
| atlassian.com | 60% | 15% | 95% |
Neither atlassian.com nor n-able.com publishes MTA-STS or TLS-RPT on the domains we audited (November 19, 2026). The low transport scores reflect that gap — relevant when fake “urgent Confluence patch” or “N-central security bulletin” messages ride the open internet.
Website stack, blacklist, and lookalikes
TLS certificates checked with openssl s_client (November 19, 2026). CMS fingerprinting was not re-run for this update.
| Domain | TLS note |
|---|---|
| atlassian.com | Amazon-issued; apex expires 2027-02-09 · www expires 2027-04-08 |
| n-able.com | Let’s Encrypt apex expires 2027-01-26 · www Google Trust Services expires 2027-01-02 |
Email blacklist checks: atlassian.com clear. n-able.com: SPFBL lists two of N-able’s EU inbound MX IPs — SPFBL inbound listings are low-weight and are not evidence N-able sends spam.
| Brand | Lookalike signal |
|---|---|
| atlassian.com | atlassianlogin.com — registered with mail (MX) but no website — a pattern consistent with BEC staging; ownership and intent not verified |
| atlassian.com | atlsasian.com — registered with mail (MX) but no website — a pattern consistent with BEC staging; ownership and intent not verified |
| n-able.com | n-able.us — registered with mail (MX) but no website — a pattern consistent with BEC staging; ownership and intent not verified |
Type Atlassian and N-able patch URLs yourself. A “Critical Axis hotfix” message pointing at a typosquat is a separate phishing risk from CVE-2026-90436 itself. Continuous monitoring: Cybersquat Domain Monitoring.
CourtListener REST search on November 19, 2026 for CVE-2026-90436 returned 0 federal docket hits. This story is vendor-advisory and researcher-led, not a named civil filing at publish time.
Related coverage
- Java4Shell — JVM Base64 flaw on Jira, Confluence, Jenkins
- FBI ARTEX FLASH — MSP OAuth chains into Microsoft 365
- MFA support directory
Sources: CISA KEV catalog · CISA catalog alert, Nov 18, 2026 · BOD 26-04 · Apache Axis CVE-2026-90436, Nov 6, 2026 · Rapid7 ETR, published Nov 16, updated Nov 19, 2026 · Atlassian CVE-2026-90436 advisory · Confluence 9.2.28 release notes · N-able remediation update · SecurityWeek N-central HF3 / 4EverAble2Shell, Nov 17, 2026 · SecurityWeek Axis + Roller roundup, Nov 19, 2026 · Apache Roller CVE-2026-129448 oss-security, Nov 17, 2026 · Microsoft security keys · Atlassian two-step verification · N-central two-factor authentication. Domain audits via admin GET /api/admin/scan?scope=full November 19, 2026; TLS via openssl November 19, 2026; blacklist, cybersquat, and CourtListener probes November 19, 2026.
Check your domain free at audit.emailmenow.com, add Domain Watch ($29/mo) for weekly mail-authentication drift checks, or see automated reports and monitoring.