Blog
Apache Axis 1.x: critical CVE-2026-90436 under active attack
What it is and who is affectedCVE-2026-90436 is an unsafe reflection vulnerability in Apache Axis, tracked by NIST's National Vulnerability Database (...
What it is and who is affected
CVE-2026-90436 is an unsafe reflection vulnerability in Apache Axis, tracked by NIST's National Vulnerability Database (NVD) as CWE-470. The flaw sits in how Axis 1.x handles an inbound SOAP fault: when a fault message carries a detail element with an exceptionName, the engine loads the class named there, and if a String data element is also present it instantiates that class through its String constructor before verifying that it is an AxisFault. Merely loading the class runs its static initialiser. With a suitable class available on the application classpath, an unauthenticated remote attacker can achieve arbitrary code execution.

Two details make this worse than a typical injection bug. First, 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. Second, the affected range is broad: NVD lists Apache Axis from 1.0 up to and including 1.4. The severity is CVSS 3.1 base score 9.8, CRITICAL (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and NVD published the record on 6 November 2026.
In practice this concerns any organisation still running a SOAP service on Axis 1.x, whether exposed directly or behind a proxy. In Spain, that pattern is common in integrations with public administrations, legacy ERP connectors and internal middleware in SMEs, ecommerce platforms and small IT teams that inherited a system years ago and never revisited it.
Why it is urgent
This is not a theoretical risk. CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities (KEV) catalogue on 18 November 2026, which means it has been observed in real attacks. CISA set a remediation deadline of 21 November 2026 for US federal agencies, requiring mitigations per vendor instructions, compliance with BOD 26-04 on risk-based security updates and the applicable forensics triage requirements, or discontinuation of the product where mitigations are unavailable. The catalogue does not record known use in ransomware campaigns.
There is a second reason for urgency: Axis 1 is end-of-life. The Apache Axis project does not expect to issue an Axis 1.x release fixing this problem, and CISA notes the product may be end-of-life or end-of-service, advising users to discontinue use or move to a supported version. There will be no convenient update to install.
What to do today
- Inventory first. Check whether any application, integration or middleware component in your estate bundles Apache Axis, and confirm the exact version. Look at dependency manifests and JAR files rather than relying on what the team remembers.
- Follow the vendor advisory. Apache recommends migrating to a different SOAP engine, such as Apache Axis 2/Java, or using a build of Axis with the patch referenced in the official advisory applied. Since no fixed 1.x release is planned, apply exactly what the vendor notice specifies rather than waiting for a version number.
- Hunt for signs of intrusion. Because the fault is parsed before service-level authentication, ordinary access logs may not show failed logins. Review SOAP traffic for unusual fault payloads and check for unexpected class loading or outbound connections from the application server.
- Reduce internet exposure. Where the service does not need to be publicly reachable, restrict it at the firewall or reverse proxy, and treat any Axis 1 endpoint still exposed as a priority.
- Align with GDPR obligations. If exploitation is suspected, assess whether personal data may have been accessed and follow your incident and notification procedures accordingly.
How a cybersecurity team can help
Legacy SOAP middleware is exactly the kind of asset that slips through the gaps: nobody owns it, no one patches it, and it rarely appears in the security roadmap. A specialist team can map what you actually run, confirm versions and exposure, and tell you which services are reachable from the internet before an attacker does. From there, the work is practical: hardening servers, closing unnecessary exposure, monitoring for the traffic patterns that precede exploitation and responding quickly if something does get through.
For businesses running WordPress, PrestaShop or Joomla alongside older integrations, the same discipline applies: keep the stack patched, audit it periodically with penetration testing, and have a clear plan for the day a site is compromised. At ALMC we work with SMEs, online shops and small IT departments across Lleida, Barcelona, Tarragona and Girona on exactly this, detecting and closing vulnerabilities before they are exploited and repairing sites that have already been hacked.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
