cve.bz

CVE-2026-97791 apache cxf: Race Condition

7.5 highEPSS 0.3%

High (7.5) in apache cxf. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-97791 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97791?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97791?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97791 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-97791

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-97791](https://cve.bz/cve/badge/CVE-2026-97791.svg)](https://cve.bz/cve/CVE-2026-97791)

HTML:

<a href="https://cve.bz/cve/CVE-2026-97791"><img src="https://cve.bz/cve/badge/CVE-2026-97791.svg" alt="CVE-2026-97791"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.4
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.9
Apache Software Foundation Apache CXFbefore 3.6.13

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in Apache CXF's STSTokenValidator, which Red Hat has rated as having Important security impact (CVSS 7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). When validating SAML tokens, STSTokenValidator checks whether an assertion is signed by a trusted certificate before deciding whether to send it to the Security Token Service (STS), and that result was stored in a single object shared across all requests. As a result, one request could read another request's validation result: a remote, unauthenticated attacker could submit a forged assertion signed with an untrusted certificate while legitimate requests were being processed and have it accepted as trusted without ever reaching the STS, bypassing authentication and gaining unauthorized access to protected application data and operations. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected.

Red Hat products that ship the affected Apache CXF cxf-rt-ws-security component, including Red Hat JBoss Fuse 7, Red Hat JBoss Enterprise Application Platform 7.4 and 8.1, and Red Hat build of Apache Camel, are affected, and fixes are being pursued for those streams. For certain streams, specifically Red Hat Single Sign-On 7 and particular JBoss EAP 7.4 container images, a fix will not be provided; those deployments remain exposed to the authentication bypass described above if STSTokenValidator is used without alwaysValidateToSts. JBoss EAP XP is not affected because the affected component is not present in it.

Red Hat's mitigation

As a workaround, configure STSTokenValidator with alwaysValidateToSts enabled so that every incoming SAML token is always sent to the Security Token Service (STS) for validation rather than being accepted based on the local certificate-trust check; services configured this way are not exposed to the shared validation state. No other mitigation is currently available beyond this configuration change and applying updates for affected products once fixed packages are released.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3cxf-rt-ws-securityAffected
Red Hat build of Apache Camel for Spring Boot 4cxf-rt-ws-securityAffected
Red Hat Fuse 7cxf-rt-ws-securityNot affected
Red Hat JBoss Enterprise Application Platform 7cxf-rt-ws-securityAffected
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Will not fix
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Affected
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Will not fix
Red Hat JBoss Enterprise Application Platform 8cxf-rt-ws-securityAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcxf-rt-ws-securityNot affected
Red Hat Single Sign-On 7cxf-rt-ws-securityWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97791.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON