{"id":"CVE-2026-90436","aliases":["DEBIAN-CVE-2026-90436","EUVD-2026-118323","GHSA-988f-c54m-f8jj","UBUNTU-CVE-2026-90436"],"status":"published","title":"Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","severity":{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-10","score":0.00567,"percentile":0.47386,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-470"],"published":"2026-11-06T15:37:55Z","modified":"2026-11-10T18:37:36Z","affected":[{"source":"osv","ecosystem":"Debian:12","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-28","1.4-28+deb12u1","1.4-29","1.4-30"]},{"source":"osv","ecosystem":"Debian:13","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-29","1.4-30"]},{"source":"osv","ecosystem":"Debian:14","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-29","1.4-30"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-22","1.4-23","1.4-24","1.4-24ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-25","1.4-25ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-28","1.4-28+deb10u1build0.20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-28","1.4-28+deb10u1build0.22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-28","1.4-29"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-29build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"axis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4-29","1.4-29build1"]}],"products":[{"vendor":"apache software foundation","product":"apache axis 1.x (eol)"}],"references":[{"url":"https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd","tags":["patch","fix","report"]},{"url":"https://lists.apache.org/thread.html/8slf0j9gz35z56t0glt5h0ncwlbn4bdz","tags":["vendor-advisory","advisory","report"]},{"url":"http://www.openwall.com/lists/oss-security/2026/11/06/12","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90436","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-988f-c54m-f8jj"},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90436.json","tags":["advisory"]},{"url":"https://gitbox.apache.org/repos/asf/axis-axis1-java.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-90436","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-90436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90436","tags":["report"]},{"url":"https://lists.apache.org/thread/8slf0j9gz35z56t0glt5h0ncwlbn4bdz","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-90436","title":"Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","status":"published","published":"2026-11-06T15:37:55.374Z","modified":"2026-11-10T18:37:36.36Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"adp"}],"cwes":["CWE-470"],"updated_at":"2026-11-10T19:39:59.74912Z"}],"euvd":[{"id":"EUVD-2026-118323","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","status":"published","published":"2026-11-06T15:37:55Z","modified":"2026-11-10T18:37:36Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-10T20:23:07.469802Z"}],"ghsa":[{"id":"GHSA-988f-c54m-f8jj","title":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x...","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","status":"published","published":"2026-11-06T18:35:15Z","modified":"2026-11-10T21:32:55Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-470"],"updated_at":"2026-11-10T21:57:51.137748Z"}],"nvd":[{"id":"CVE-2026-90436","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","status":"published","published":"2026-11-06T16:18:59.763Z","modified":"2026-11-10T19:21:35.7Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"secondary"}],"cwes":["CWE-470"],"updated_at":"2026-11-10T22:21:31.83577Z"}],"osv":[{"id":"CVE-2026-90436","title":"Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.\n\n\n\nAs 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.","status":"published","published":"2026-11-06T15:37:55.374Z","modified":"2026-11-11T13:26:44.704604598Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-470"],"updated_at":"2026-11-11T11:06:54.350472Z"},{"id":"DEBIAN-CVE-2026-90436","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.","status":"published","published":"2026-11-06T16:18:59.763Z","modified":"2026-11-11T10:01:28.1047285Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-11T10:35:16.464644Z"},{"id":"UBUNTU-CVE-2026-90436","description":"** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP \u003cFault\u003e carries a \u003cdetail\u003e\u003cexceptionName\u003e element, Axis loads the named class and, if a String \u003cdata\u003e 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.","status":"published","published":"2026-11-09T00:00:00Z","modified":"2026-11-10T02:52:13.868387659Z","updated_at":"2026-11-10T03:20:58.564844Z"}]}}