endoflife.ai
Exploited & Unpatchable EOL Watch How we verify

Apache Axis CVE-2026-90436 on CISA KEV: Axis 1 Is EOL, No Release

By Scott Bissett  ·  Published: November 19, 2026  ·  EOL Watch — news analysis  ·  Read at Apache's advisory on its mailing list, the CVE record Apache wrote, the Axis project page and CISA's catalog

Apache Axis 1 is end of life, it has a critical flaw that is being exploited, and Apache does not plan a release that fixes it. CISA put CVE-2026-90436 on its Known Exploited Vulnerabilities catalog on November 18, 2026. Apache's advisory, published on November 6, 2026, is titled “Apache Axis 1.x (EOL)” and ends with this sentence: “The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.”

The lifecycle fact that decides what you do next. There is no fixed Axis 1 version to upgrade to. Apache's advisory says “This affects all Apache Axis 1.x versions through 1.4,” and the newest release announced on the Axis project page is Axis 1.4 Final, on April 22, 2006. Apache's advice is to leave Axis 1: “As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java.”

What the flaw is

CVE-2026-90436 is an unsafe reflection flaw in how Axis 1 reads an incoming SOAP fault. Apache's advisory says it “allows unauthenticated remote class instantiation”: when a SOAP fault carries an exception name, “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.” It continues: “With a suitable class on the application's classpath this leads to remote code execution.” Apache rates the severity critical.

Authentication on the service does not stop it. In Apache's words, “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.”

The CVE record carries the tag “unsupported-when-assigned”, and its description opens with “UNSUPPORTED WHEN ASSIGNED”: the product was already out of support when the flaw was recorded.

Running Apache Axis past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers Apache Axis is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

What Apache lists as affected, and what it offers

The rows below are Apache's advisory and the CVE record Apache wrote, word for word where quoted.

WhatApache's statement
Product“Apache Axis 1.x (EOL)”
Affected versions“all Apache Axis 1.x versions through 1.4”
Packages named in the CVE recordaxis:axis and org.apache.axis:axis, each through 1.4
Fixed releaseNone. “The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.”
Source patch“Alternatively you could use a build of Axis with the patch from” this commit in Apache's Axis 1 repository “applied.”
Recommended move“migrate to a different SOAP engine, such as Apache Axis 2/Java”

The advisory names Axis 1.x only. It does not list Apache Axis2 as affected, and it names Axis 2/Java as one place to go.

What Apache has not said. Apache's pages do not give the day Axis 1 became end of life; the advisory says only that it “has been EOL.” Apache has not published a patched binary, only the source change. And it has not listed which products bundle Axis 1. CISA's entry makes the same point from the other side: “This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products.”

What CISA's entry says

CISA's entry names the vendor as Apache and the product as Axis. It was added on November 18, 2026 with a due date of November 21, 2026 for federal civilian agencies, and it lists ransomware use as Unknown.

CISA states the end-of-life position in the entry itself: “The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.” Its required action is to apply the vendor's mitigations “or discontinue use of the product if mitigations are unavailable.”

What to do

Find it first. Axis 1 is a library, so it sits inside other applications. The CVE record gives the two Maven names to search your builds and software bills of materials for: axis:axis and org.apache.axis:axis, any version through 1.4.

Plan the move off Axis 1. This is Apache's recommendation, and it is the only route that ends on supported software: “migrate to a different SOAP engine, such as Apache Axis 2/Java.”

If you cannot move yet: Apache's alternative is to build Axis yourself with its patch applied. That is a source change you compile and ship; Apache does not expect to publish an Axis 1.x release that contains it.

Do not rely on service authentication. Apache says authentication handlers configured on a service do not protect against this flaw.

If Axis 1 came inside a product you bought: the fix has to come from that product's vendor. Ask whether the product bundles Axis 1 and whether a build with Apache's patch is available.

Federal agencies: CISA's due date is November 21, 2026, under BOD 26-04. CISA's required action is to apply the vendor's mitigations or discontinue use of the product if mitigations are unavailable.

Frequently Asked Questions

Is there a fixed version of Apache Axis 1 for CVE-2026-90436?

No fixed release exists, and Apache does not plan one. Apache's advisory says: The Apache Axis project does not expect to create an Axis 1.x release fixing this problem. Apache published a source patch instead and says you could use a build of Axis with that patch applied. Its main recommendation is to migrate to a different SOAP engine, such as Apache Axis 2/Java.

Which Apache Axis versions are affected by CVE-2026-90436?

Apache's advisory says the flaw affects all Apache Axis 1.x versions through 1.4. The CVE record lists two Maven packages, axis:axis and org.apache.axis:axis, each through 1.4. The advisory names Axis 1.x only and does not list Apache Axis2 as affected.

Is Apache Axis 1 end of life?

Yes, in Apache's own words. The advisory is titled Apache Axis 1.x (EOL), carries the CVE tag unsupported-when-assigned, and says: As Axis 1 has been EOL we recommend you migrate to a different SOAP engine. Apache's pages do not give the day Axis 1 became end of life. The newest release announced on the Axis project page is Axis 1.4 Final, on April 22, 2006.

What is the CISA deadline for CVE-2026-90436?

CISA added CVE-2026-90436 to the Known Exploited Vulnerabilities catalog on November 18, 2026 with a due date of November 21, 2026 for federal civilian agencies. CISA's entry says the impacted product could be end-of-life or end-of-service and advises users to discontinue use or transition to a supported version. CISA lists ransomware use as Unknown.

Do authentication handlers protect an Axis 1 service from CVE-2026-90436?

Not according to Apache. The advisory says 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. Apache also says exploitation needs a suitable class on the application's classpath.

Related

© 2026 endoflife.ai · How we verify our dates · API · About