CVE-2026-97791: high-severity vulnerability in Apache CXF
Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.3%
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.
Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
Apache Software Foundation · Apache CXFRelated CVEs — Apache CXF
In the same product, most dangerous first.
CVE-2020-13954—Apache CXF Reflected XSS in the services listing page via the styleSheetPathEPSS 40.9%CVE-2017-5653—CVE-2017-5653EPSS 11.2%CVE-2018-8039—CVE-2018-8039EPSS 8.5%CVE-2016-6812—CVE-2016-6812EPSS 7.5%CVE-2016-8739—CVE-2016-8739EPSS 7.3%CVE-2021-30468—Apache CXF Denial of service vulnerability in parsing JSON via JsonMapObjectReaderWriterEPSS 7.0%