CISA added Apache Axis 1’s CVE-2026-90436 to its Known Exploited Vulnerabilities catalog on November 18. The retired Java component can turn an incoming SOAP error message into code execution. Apache recommends migration and does not expect to publish an Axis 1.x release fixing it.
Robert Lazarski’s Apache advisory was published November 6. The new development is CISA’s exploitation listing, not a newly disclosed vulnerability or a known first-attack date.
Service authentication happens after the dangerous parsing
Axis implements SOAP, an XML-based protocol for application messages. The defect affects all Apache Axis 1.x versions through 1.4. Apache’s CVE record identifies the Maven packages axis:axis and org.apache.axis:axis. A product can therefore inherit exposure through a bundled library rather than a separately installed server.
While interpreting an incoming fault, Axis loads a class named by the message and may create an instance before checking its expected type. Loading a class can itself run initialization code. Code execution requires a suitable class already available to the application, so installed dependencies affect the outcome.
The fault is parsed while Axis resolves the target service, before that service’s handler chain runs. Apache explicitly warns that authentication handlers configured on a service do not protect this path. An operator cannot count a service-level login requirement as proof that the earlier parser is protected.
Evidence status: exploitation reported by CISA. The CVE record’s CISA assessment also marks exploitation active. Neither public source supplies a campaign account, named victims or a measured compromise count. The catalog’s ransomware-use field remains Unknown.
A source patch exists, but no repaired Axis 1 release is promised
Apache recommends moving to a different SOAP engine, giving Apache Axis 2/Java as an example. That is a migration between products, not an instruction to change a version number and assume compatibility.
Apache also permits using a build with its published source patch applied. The repair limits accepted classes to the intended fault type and avoids initializing an arbitrary class while checking it. The exact commit is:
41f3b4e8d04e310ca81f86b92630ab2c11d608bd
The project says it does not expect to create a fixing Axis 1.x release. There is no official repaired release number to substitute for 1.4 in a patch checklist. A source-patched build still needs an owner, release provenance and application-compatibility testing.
For operators and application teams:
- Use dependency inventories and vendor documentation to locate Axis 1, including libraries bundled into deployed applications. Ask the product vendor whether its build contains the named repair.
- Establish whether untrusted messages can reach the affected parser. Service authentication alone cannot answer that question.
- Plan a supported-engine migration or obtain a demonstrably patched build. Verify the artifact actually deployed and its application behavior.
- While arranging repair, restrict untrusted access to the affected service at an earlier boundary. This is a containment measure, not an upstream claim that a particular gateway rule fixes the parser.
Preserve evidence from earlier exposure
The CISA catalog flags this entry for forensic triage, an initial investigation of possible compromise. Its listed due date is November 21. Federal obligations depend on BOD 26-04 and asset exposure; that date is not a universal deadline for every operator.
CISA’s triage guidance calls for preserving volatile evidence and persistent records before changes erase them, where possible. Coordinate that collection with containment and remediation. Review unauthorized access, unexpected processes, persistence and possible data removal. These are general investigation questions, not campaign-specific indicators published for this flaw.
A migrated or patched application can still require incident response for earlier exposure. Completing the repair does not establish that its old installation was never compromised.
Caveat: Exploitation is documented at the catalog level; the reviewed sources give no public incident narrative or full third-party-product exposure matrix. Migration compatibility and any vendor backport must be verified for the actual application.