Skip to content
fr Sign in
Not rated

CVE-2026-97791 In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to…

Description

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.

Affected products and versions

Product Affected versions Fixed in
Apache CXF 4.2 4.2.0 → < 4.2.4 4.2.4
Apache CXF 4.0 4.0.0 → < 4.1.9 4.1.9
Apache CXF 3.6 earliest → < 3.6.13 3.6.13

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache CXF

The 56 CVEs of Apache CXF →
CVE-2026-108039 By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML… Not rated CVE-2026-107938 In Apache CXF, the Netty-based HTTP client transport (cxf-rt-transports-http-netty-client) did not verify that the… Not rated CVE-2026-107937 In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured… Not rated CVE-2026-100227 Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security module Not rated
Track this CVE