{"dataType": "CVE_RECORD", "containers": {"adp": [{"metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}}, {"other": {"type": "Unknown", "content": {"data": "{\"description\":\"Important\"}"}}}], "affected": [{"vendor": "redhat", "product": "axis", "platforms": ["cpe:/o:redhat:enterprise_linux:6"], "defaultStatus": "affected"}, {"vendor": "redhat", "product": "axis-javadoc", "platforms": ["cpe:/o:redhat:enterprise_linux:6"], "defaultStatus": "affected"}, {"vendor": "redhat", "product": "axis-manual", "platforms": ["cpe:/o:redhat:enterprise_linux:6"], "defaultStatus": "affected"}], "references": [{"url": "https://access.redhat.com/security/cve/CVE-2026-90436"}], "descriptions": [{"lang": "en", "value": "A flaw was found in Apache Axis. An unauthenticated remote attacker can exploit an insecure deserialization issue by sending a specially crafted Simple Object Access Protocol (SOAP) fault message. Because the message is parsed and classes are instantiated before authentication handlers are evaluated, an attacker can achieve arbitrary code execution if a suitable class is present on the application's classpath. \n            This vulnerability is rated as Important severity because an unauthenticated network attacker can trigger class instantiation before service handlers run, though achieving code execution relies on specific gadget classes existing within the runtime classpath. In Red Hat deployments where legacy Axis 1.x libraries are bundled into Java enterprise applications, incoming SOAP requests are processed prior to authentication, leaving exposed endpoints vulnerable to remote manipulation. However, the prerequisite of having an exploitable class on the classpath raises the attack complexity and prevents indiscriminate exploitation.\n            Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.\n\n--- CME Mitigation Guidance (2026-11-06) ---\nDisclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.\n\nThe highest-value action is to eliminate unsafe reflection and arbitrary class loading in SOAP fault detail parsing by restricting instantiation exclusively to verified AxisFault subtypes: upgrade to the fixed release, which load classes without initialization and verify they are assignable to AxisFault before invoking constructors, closing all 2 injection vectors (crafted SOAP Fault detail exceptionName element triggering static class initialization, crafted SOAP Fault detail exceptionName and data elements invoking single-argument String constructor). Until patched, this is a concern on applications exposing Apache Axis 1.x SOAP endpoints with gadget classes on the classpath, so restrict network access to exposed Axis endpoints and audit runtime classpaths to remove exploitable gadget classes containing dangerous static initializers or single-argument String constructors. As a compensating measure, apply strict allowlist validation to the exceptionName input to block attacker-supplied class names from reaching the dynamic class loader. These controls limit blast radius and contain exploitation, but they do not fix the underlying unsafe reflection defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}], "providerMetadata": {"orgId": "53f830b8-0a3f-465b-8143-3b8a9948e749", "shortName": "redhat", "dateUpdated": "2026-11-06T15:37:00Z", "x_subShortName": "redhat_6"}}, {"metrics": [{"other": {"type": "Unknown", "content": {"data": "{\"description\":\"not yet assigned\"}"}}}], "affected": [{"vendor": "debian", "product": "libaxis-java", "platforms": ["forky", "sid"], "defaultStatus": "affected"}, {"vendor": "debian", "product": "axis", "platforms": ["bookworm", "trixie"], "defaultStatus": "unaffected"}], "references": [{"url": "https://security-tracker.debian.org/tracker/CVE-2026-90436"}], "descriptions": [{"lang": "en", "value": "** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, 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. 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."}], "providerMetadata": {"orgId": "79363d38-fa19-49d1-9214-5f28da3f3ac5", "shortName": "debian", "dateUpdated": "2026-11-06T15:37:55.374Z", "x_subShortName": "debian"}}, {"metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}}, {"other": {"type": "Unknown", "content": {"data": "{\"description\":\"medium\"}"}}}], "affected": [{"vendor": "canonical", "product": "libaxis-java", "platforms": ["bionic", "jammy", "noble", "resolute"], "defaultStatus": "unknown"}], "references": [{"url": "https://ubuntu.com/security/CVE-2026-90436"}, {"url": "https://www.cve.org/CVERecord?id=CVE-2026-90436"}], "descriptions": [{"lang": "en", "value": "** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP &lt;Fault&gt; carries a &lt;detail&gt;&lt;exceptionName&gt; element, Axis loads the named class and, if a String &lt;data&gt; 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."}], "providerMetadata": {"orgId": "cc1ad9ee-3454-478d-9317-d3e869d708bc", "shortName": "canonical", "dateUpdated": "2026-11-06T16:18:00Z", "x_subShortName": "canonical"}}], "cna": {"tags": ["unsupported-when-assigned"], "metrics": [{"format": "CVSS", "cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}}], "affected": [{"vendor": "unknown", "product": "unknown", "defaultStatus": "unknown"}], "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/11/06/12"}, {"url": "https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd"}, {"url": "https://lists.apache.org/thread.html/8slf0j9gz35z56t0glt5h0ncwlbn4bdz"}], "descriptions": [{"lang": "en", "value": "** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, 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. 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."}], "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-470", "description": "CWE-470"}]}], "providerMetadata": {"orgId": "00000000-0000-4000-A000-000000000003", "shortName": "DISCARDED_CNA", "dateUpdated": "2026-11-06T16:18:59Z", "x_subShortName": "nvd"}}}, "cveMetadata": {"cveId": "CVE-2026-90436", "state": "PUBLISHED", "dateUpdated": "2026-11-10T19:21:35Z", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "datePublished": "2026-11-06T16:18:59Z", "assignerShortName": "apache"}, "dataVersion": "5.0"}