CVE-2026-71575
Received Received - Intake

OidcClientCodeRequestFilter Authentication Bypass via Max-Age Misconfiguration

Vulnerability report for CVE-2026-71575, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-09

Last updated on: 2026-10-09

Assigner: Apache Software Foundation

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-09
Last Modified
2026-10-09
Generated
2026-10-09
AI Q&A
2026-10-09
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
Apache Software Foundation Apache CXF 4.2.0
Apache Software Foundation Apache CXF 4.0.0
Apache Software Foundation Apache CXF 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-613 According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a unit mismatch in the max_age authentication check in OidcClientCodeRequestFilter. The check was supposed to compare session age in seconds but used milliseconds instead, and the comparison logic was inverted. This caused the system to incorrectly accept sessions of any age, bypassing re-authentication requirements.

Detection Guidance

This vulnerability is specific to Apache CXF's OidcClientCodeRequestFilter and involves a logic error in authentication freshness checks. Detection requires verifying the version of Apache CXF in use and checking if setMaxAgeOffset is configured. No direct network or system commands are provided in the context to detect this issue.

Impact Analysis

If you use Apache CXF with OIDC authentication and rely on max_age to enforce re-authentication, this flaw could allow unauthorized access to protected resources. Attackers might exploit it to bypass step-up authentication policies, potentially gaining access to sensitive data or functions without proper re-verification.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR, HIPAA, or other regulations requiring strong authentication and session management. Bypassing re-authentication may violate access control requirements, potentially resulting in data breaches or unauthorized disclosures.

Mitigation Strategies

Upgrade Apache CXF to version 4.2.4, 4.1.9, or 3.6.13 or later to fix the max_age authentication-freshness check issue. If upgrading is not immediately possible, review and adjust authentication policies to ensure step-up authentication is enforced independently of setMaxAgeOffset.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71575. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart