CVE-2026-97791
published 2026-10-09CVE-2026-97791: 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…
PriorityP346high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.30%
22.2th percentile
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
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | cxf | < 3.6.13 | 3.6.13 |
| apache | cxf | >= 4.0.0 < 4.1.9 | 4.1.9 |
| apache | cxf | >= 4.2.0 < 4.2.4 | 4.2.4 |
| apache_software_foundation | apache_cxf | < 3.6.13 | 3.6.13 |
| apache_software_foundation | apache_cxf | >= 4.0.0 < 4.1.9 | 4.1.9 |
| apache_software_foundation | apache_cxf | >= 4.2.0 < 4.2.4 | 4.2.4 |
| jboss-eap-7 | eap74-els-openjdk11-openshift-rhel8 | — | — |
| jboss-eap-7 | eap74-els-openjdk17-openshift-rhel8 | — | — |
| jboss-eap-7 | eap74-els-openjdk8-openshift-rhel8 | — | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vendor_redhat7.4HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
org.apache.cxf/cxf-rt-ws-security: Apache CXF: Authentication bypass via shared token validation state
vendor_redhat·2026-10-09·CVSS 7.4
CVE-2026-97791 [HIGH] CWE-488 org.apache.cxf/cxf-rt-ws-security: Apache CXF: Authentication bypass via shared token validation state
org.apache.cxf/cxf-rt-ws-security: Apache CXF: Authentication bypass via shared token validation state
A flaw was found in Apache CXF. This vulnerability allows an authentication bypass when validating Security Assertion Markup Language (SAML) tokens. Because the token validator shares validation state across concurrent requests, a remote, unauthenticated attacker can submit a forged assertion signed with an untrusted certificate while legitimate requests are processed, causing the forged assertion to be accepted as trusted.
Package: cxf-rt-ws-security (Red Hat build of Apache Camel 4 for Quarkus 3) - Affected
Package: cxf-rt-ws-security (Red Hat build of Apache Camel for Spring Boot 4) - Affected
Package: cxf-rt-ws-security (Red Hat Fuse 7) - Affected
Package: cxf-rt-ws-security (Red
GHSA
In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS.
ghsa_unreviewed·2026-10-09
CVE-2026-97791 In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS.
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.
No detection rules found.
No public exploits indexed.
2026-10-09
Published