{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-97791", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2026-09-25T04:38:00.142Z", "datePublished": "2026-10-09T10:19:26.153Z", "dateUpdated": "2026-10-09T10:19:26.153Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-10-09T10:19:26.153Z"}, "title": "Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests", "source": {"discovery": "UNKNOWN"}, "affected": [{"vendor": "Apache Software Foundation", "product": "Apache CXF", "packageURL": "pkg:maven/org.apache.cxf/cxf-rt-ws-security", "versions": [{"status": "affected", "version": "4.2.0", "lessThan": "4.2.4", "versionType": "semver"}, {"status": "affected", "version": "4.0.0", "lessThan": "4.1.9", "versionType": "semver"}, {"status": "affected", "version": "0", "lessThan": "3.6.13", "versionType": "semver"}], "defaultStatus": "unaffected", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.cxf:cxf-rt-ws-security"}], "descriptions": [{"value": "In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another's result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected.\u00a0\nUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.", "lang": "en", "supportingMedia": [{"type": "text/html", "base64": false, "value": "In Apache CXF, <code>STSTokenValidator</code> checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another's result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use <code>STSTokenValidator</code> to validate SAML tokens without <code>alwaysValidateToSts</code> set are affected.&nbsp;<br>Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue."}]}], "references": [{"url": "https://lists.apache.org/thread.html/ssdr417qgms9fjl0m8802xd8170wnk1l", "tags": ["vendor-advisory"]}], "metrics": [{"other": {"type": "Textual description of severity", "content": {"text": "important"}}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "credits": [{"lang": "en", "value": "MopMonk-AI", "type": "finder"}], "x_generator": {"engine": "Vulnogram 1.0.3"}}}}

{}

{}

{}

{}