Koffei

CVE-2026-90436

🔴 High In CISA KEV

Apache Axis 1.x (end of life), embedded in products such as N-able N-central (the 4EverAble2Shell chain) · All Axis 1.x through 1.4

CVSS (Koffei note)
9.8
CVSS (v3.1, CVE List)
9.8
EPSS (2026-11-18)
1.128%
67.01th percentile
CISA KEV
2026-11-18
due 2026-11-21

Exploitation

Yes — CISA KEV since 18/11/2026 (due 21/11/2026, ransomware use: Unknown; read from the CISA catalog on 19/11/2026). Correction 19/11/2026: the row previously read "Probable" and "Not in KEV"; the KEV listing confirms exploitation. Re-tested 19/11/2026: the KEV listing is 1 days old, inside the 60-day window, so 🟠 → 🔴. Previous text: Probable — reported exploited inside the N-central 4EverAble2Shell chain: The Hacker News (13/11/2026), citing Huntback, says the chain (this flaw plus an N-central privilege escalation with no CVE) dropped an XMRig miner on 21 N-central servers, 19 of them already on Hotfix 2; Presidian saw probing from 157.20.241[.]16 on 11-12/11/2026. Single-source: the enrichment pass found no second report and no Huntback publication, and CISA-ADP SSVC still reads exploitation none / automatable yes (10/11/2026, now stale against the press report). Not in KEV (mirror current to 10/11/2026). Rated 🟠 (probable exploitation, no upstream fix); re-test for 🔴 once a second source or KEV confirms. cyberveille RSS: checked, no result

Timeline

  1. 06/11/2026CVE record published (CVE List)
  2. 12/11/2026New N-central exploits bypass N-able's hotfix ("4EverAble2Shell", "Agent2Shell")
  3. 13/11/2026N-central exploit chain now used to drop miners on 21 servers, 19 of them already on Hotfix 2
  4. 18/11/2026N-able ships N-central 2026.4 HF3 for 17 flaws and kills the legacy API; the Axis bug behind it is also hitting Confluence
  5. 18/11/2026Added to the CISA KEV catalogue
  6. 19/11/2026CISA adds four exploited flaws to KEV: Apache Axis, REDCap, Synology DSM and LiteLLM
  7. 21/11/2026CISA deadline for US federal agencies

Risk

9.8 Critical (v3.1, CISA-ADP; Apache rates it critical with no score) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS 1.128% (OpenCVE) (CWE-470 unsafe reflection: the exceptionName of a SOAP fault makes Axis instantiate an attacker-chosen class before the service handler chain runs, so authentication handlers do not protect it; pre-auth RCE)

Fix

No — Apache will not release a fix for Axis 1.x: migrate to Axis2 or apply upstream commit 41f3b4e (Apache announcement); for N-central, N-able advises agents and probes on 2026.4 HF1 or later, and Huntback says Hotfix 2 alone is not enough

Official description

** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-470