Skip to content
Fencer Intel
critical 9.1

CVE-2026-71575 json

Apache CXF: Inoperative max_age authentication-freshness check in OidcClientCodeRequestFilter

published last mo. modified 26d ago also EUVD-2026-95694

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

The max_age authentication-freshness check in OidcClientCodeRequestFilter was inoperative due to a milliseconds/seconds unit mismatch and an inverted comparison polarity. Any relying party using setMaxAgeOffset to enforce re-authentication would silently accept sessions of any age, bypassing step-up authentication policies. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

Patch / fix

  • maven org.apache.cxf:cxf-rt-rs-security-sso-oidc 3.6.13, 4.1.9, 4.2.4
  • Apache Software Foundation Apache CXF 3.6.13, 4.1.9, 4.2.4

Is CVE-2026-71575 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-71575 updated cvss 5.4

org.apache.cxf/cxf-rt-rs-security-sso-oidc: Apache CXF: Re-authentication bypass via improper session freshness check

  • Red Hat build of Apache Camel for Spring Boot 4 cxf-rt-rs-security-sso-oidc 4.1.8.rhbac-redhat-00002
    affected: no fix available “Fix deferred”
  • Red Hat Fuse 7 cxf-rt-rs-security-sso-oidc 4.1.8.rhbac-redhat-00002 Red Hat JBoss Web Server 5 cxf-rt-rs-security-sso-oidc 4.1.8.rhbac-redhat-00002
    affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
27d ago

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.cxf:cxf-rt-rs-security-sso-oidc
>=4.2.0, <4.2.4
>=4.0.0, <4.1.9
<3.6.13
4.2.4
4.1.9
3.6.13

Affected products

  • Apache Software Foundation Apache CXF

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.