On November 18, 2026, CISA added CVE-2026-90436 for Apache Axis—unsafe reflection when inbound SOAP Fault messages carry attacker-controlled exceptionName (and optional data) values. Axis 1.x through 1.4 loads and can instantiate arbitrary classes before authentication handlers run, yielding remote code execution when a suitable classpath gadget exists. Apache announced Axis 1 is end-of-life in the oss-security disclosure and points to commit 41f3b4e or migration to Axis 2/Java.
If coding agents refactor legacy Java without removing axis-1.4.jar, this KEV entry is a reminder to grep dependencies before shipping.
TL;DR
| Question | Answer |
|---|---|
| Exploited? | Yes — KEV 2026-11-18 |
| Federal due date? | 2026-11-21 (short fuse) |
| Affected | Axis 1.x ≤ 1.4 |
| Official release? | None planned |
| Mitigation | Patch commit, migrate, or remove exposure |
| BOD forensics? | Yes — triage required per KEV row |
Historical context: EOL SOAP stacks in 2026
Apache Axis 1 reached end of life years ago, yet SOAP fault endpoints remain in healthcare, government, and finance integrations—exactly the systems coding agents are asked to wrap with REST without deleting legacy servlets. CVE-2026-90436 is a parser-ordering bug: fault XML is handled before operators expect authentication to matter.
That ordering breaks mental models where teams say “our Axis endpoint requires a token.” The token check may live in a handler that never runs if fault deserialization already executed static initializers on a gadget class.
Mechanism step by step
From Apache’s oss-security post and Red Hat’s CVE statement:
- Attacker sends SOAP request whose body includes a Fault with detail/exceptionName (and optionally data).
- Axis parses the fault while resolving the service, before the per-service handler chain (where auth often lives).
- Axis loads the named class; static initializers may run on load.
- If String data is present, Axis may invoke a String constructor before verifying AxisFault subtype.
- With gadgets (vendor write-ups cite examples like Spring ClassPathXmlApplicationContext chains), attackers reach RCE.
The upstream commit message explains the fix: load classes without initialization, accept only AxisFault subtypes, and gate reflective constructors.
Fix and migration paths
| Option | Action |
|---|---|
| Migrate | Move services to Axis 2/Java or non-SOAP APIs agents can maintain with tests |
| Vendor patch build | Internal fork with 41f3b4e applied |
| Compensating | Network restrict SOAP endpoints; audit classpath for gadgets (Java4Shell agent discovery context) |
Debian security tracker shows axis 1.4 packages still vulnerable in stable suites—container images agents generate may inherit that.
What this means if you run AI coding agents
Agents excel at wrapping old SOAP services with REST facades but often leave Axis jars in WEB-INF/lib. Combine:
mvn dependency:treeorgradle dependenciesin CI gates agents edit- Beam hook denies on agents deleting security tickets or skipping dependency scans
- Separate internet exposure for legacy SOAP paths agents call via integration tests
Beam does not scan JVM classpaths; local policy and human review on agent-produced pom.xml / build.gradle changes remain necessary.
Why authentication handlers do not help
Apache’s disclosure stresses fault parsing during service resolution—before per-service handler chains that often enforce WS-Security, HTTP basic, or custom tokens. Pen testers frequently file bugs as “auth bypass” when the real issue is earlier parser logic; this is that pattern on SOAP Fault XML.
Implication for agent-maintained Java: adding Spring Security around the controller does not retroactively protect Axis servlet entrypoints still mapped in web.xml.
Gadget classpath reality on developer machines
Exploitation is not magic without gadgets—Red Hat rates Important partly because RCE depends on classpath contents. In enterprise apps, legacy Spring, Commons Collections, and custom String constructors still appear in WAR files agents “modernize” by wrapping with REST.
Agent task: run dependency scans before and after refactors:
mvn -q dependency:tree -Dincludes=org.apache.axis:axis
gradle dependencies --configuration runtimeClasspath | grep axis
If Axis 1 remains, ticket removal beats LLM-generated OpenAPI facade alone.
Building Axis 1 with commit 41f3b4e
Apache will not ship 1.4.1. Maintainers must:
- Clone axis-axis1-java.
- Cherry-pick or checkout 41f3b4e8d04e310ca81f86b92630ab2c11d608bd.
mvn installto internal artifact repo.- Pin internal coordinates in builds agents touch.
The commit adds regression tests that fail on vulnerable fault deserialization—wire those tests into CI so agents cannot revert the fork silently.
KEV short due date (November 21, 2026)
CISA’s 2026-11-18 KEV row sets due date 2026-11-21—a three-day federal window, typical for actively exploited internet-facing services. Private teams should treat Friday, November 21 as a hard inventory deadline even if BOD 26-04 does not bind you.
Forensic triage: Yes on the catalog row—assume compromise assessment if Axis endpoints were public since November 2026.
Debian and container base images
Debian tracker marks axis 1.4 vulnerable in bookworm/trixie without an upstream fixed version in distro—containers agents generate from openjdk:*-bookworm may embed vulnerable axis jars via transitive deps. Scan OCI images in registries agents push to.
Axis in the supply chain agents inherit
Axis 1.x persists in ERP connectors, hospital HL7 bridges, legacy government SOAP, and fat JARs checked into repos agents summarize as “unmaintained but working.” When agents containerize those apps without dependency hygiene, they copy vulnerable axis.jar into new attack surface on Kubernetes.
Run software composition analysis on any image an agent builds; axis:1.4 should trigger fail CI until removed or patched fork lands.
Coordination with November 18 KEV cluster
The same CISA catalog update added LiteLLM, REDCap, Synology, and Axis—a reminder that KEV days are seldom one-product stories. Platform teams should batch change advisory review, while agent teams should avoid scheduling Friday mass refactors on the same weekend infra must patch.
SOAP exposure reduction
Until migration:
- Remove public SOAP listeners where REST replacements exist.
- mTLS or IP allowlist on legacy endpoints—does not fix bug but cuts noise.
- Disable WSDL discovery on edge if still enabled.
Frequently asked questions
Is CVE-2026-90436 the same as Log4Shell?
No—different chain (SOAP Fault exceptionName vs JNDI lookup), though both are unauth RCE on Java stacks agents operate on.
Will Axis 1.4.1 release?
Apache said no planned 1.x release—oss-security.
How does Beam help?
Hook-based deny on agents deleting security scan steps or web.xml diff without review—heuristic, not SOAP-aware.
What if my agent only added a REST shim?
Shim does not remove Axis servlet unless deployment descriptor changes—verify both paths.
Link to related KEV infrastructure?
See Puppet Enterprise KEV for another fleet-wide Java-adjacent config risk pattern.
Sample SOAP fault shape (conceptual)
Defenders hunting in WAF logs look for SOAP envelopes where Fault/detail contains exceptionName referencing non-application packages (org.springframework..., com.sun...) or data elements with long base64 blobs. The oss-security post does not mandate a public PoC XML sample, but class name leakage in 400/500 responses after failed exploitation attempts is a common IDS signature.
Red Hat’s mitigation text (November 2026) mentions allowlist validation on exceptionName as compensating control—use only until 41f3b4e build ships; allowlists drift when agents add new JARs to classpath.
Agent CI guardrails for Java refactors
Add policy to agent harnesses:
- Deny merging
build.gradlechanges that re-introduceorg.apache.axis:axiswithout security review ticket. - Require
dependency:treeartifact on every agent-opened Java PR. - Block Dockerfile
COPYlines that embed prebuilt WARs without SBOM.
Beam PreToolUse hooks can warn on axis-1.4.jar appearing in Write tool paths when configured with custom patterns—still heuristic, but better than silent acceptance.
Migration options when agents own the backlog
Option A — Strangle the servlet: Stand up a small REST BFF agents maintain, move callers to JSON, retire SOAP listener on the edge load balancer first so exposure drops even while Axis remains in the WAR temporarily.
Option B — Fork Axis: Internal Maven coordinate com.yourorg:axis-patched:1.4.0-sp1 built from 41f3b4e; pin in BOM files agents must not override.
Option C — Full removal: Replace with Axis2, JAX-WS, or gRPC—higher cost, only when business mandates.
Document the chosen option in architecture decision records so the next agent session does not re-add axis:1.4 from Stack Overflow snippets.
Openwall disclosure as authoritative primary
The oss-security mail is the canonical public description Apache expects vendors to cite. When NVD shows “Unsupported when assigned,” procurement teams may ask whether you must fix—KEV answers yes for US federal contractors and is a risk signal for everyone else.
Classpath gadget hygiene checklist
Walk every WAR and Spring Boot fat jar on hosts agents deploy to:
| Gadget family | Why it matters to Axis chain |
|---|---|
| Spring ClassPathXmlApplicationContext | Named in Apache commit message as example |
| Commons Collections transformers | Historical deserialization chains |
Custom String ctor classes | Axis may instantiate via String data element |
Remove unused JARs rather than relying on WAF alone—agents love copying full lib/ directories from tutorials.
Red Hat and Rapid7 vendor nuance
Rapid7’s database entry repeats Apache’s CVSS 9.8 vector for prioritization dashboards. Red Hat rates Important because gadget requirement lowers practical exploitability on minimal classpaths—KEV still overrides for exposed endpoints.
When agents file JIRA tickets, include both scores plus internet exposure boolean so owners do not dismiss the bug as theoretical.
Testing patched builds safely
Stand up a disposable Tomcat + vulnerable Axis WAR only on an isolated VLAN for validation—never on production VLAN agents share with corporate LDAP. After applying 41f3b4e, replay Securifera-style negative tests (malformed Fault should not instantiate non-AxisFault classes).
Record results in change ticket attached to Docker image digest agents later deploy—prevents “we thought we patched” drift when base image updates silently.
Federal due date pressure (November 21, 2026)
The three-day KEV window ending November 21 overlaps weekend on-call for many Java shops. Pre-stage maintenance notifications Friday morning so agent-driven deploy pipelines do not auto-promote Friday night builds that still bundle axis-1.4.jar. If you cannot migrate by the due date, document compensating network blocks and executive risk acceptance—CISA’s catalog is explicit about exploitation, not theoretical risk scoring alone.
Ask application owners whether SOAP listeners are still business-critical or only legacy batch jobs agents were supposed to retire last quarter—sunset decisions accelerate faster when KEV due dates sit 72 hours away. Capture SOAP endpoint inventory in the same spreadsheet you use for LLM gateway URLs so agent routing changes do not hide forgotten Axis paths.
Related reading
- Java4Shell and agent CVE discovery
- FreeSWITCH KEV RCE
- November attacks timeline
- Coding assistant security solutions
Apache Axis 1 is EOL; treat KEV as migrate-or-fork, not wait-for-point-release.

