CVE-2026-97791CWE-362

CVE-2026-97791

High · published October 9, 2026

CVSS v3.1
7.5
EPSS
0%
Percentile
22.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.5 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00305 · 22.1th percentile
Weakness
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Published
2026-10-09T15:17Z
Affected products (3)
ProductVersionsFixed in
apache/cxf< 3.6.133.6.13
apache/cxf≥ 4.0.0, < 4.1.94.1.9
apache/cxf≥ 4.2.0, < 4.2.44.2.4
References (2)
EPSS history
Timeline
  • 11 OCT 03:33Z
    EPSS moved — → 0%
    epss
  • 09 OCT 10:19Z
    Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests
    cvelistv5
  • 09 OCT 10:19Z
    Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests
    cvelistv5