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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://lists.apache.org/thread/p1r9t4xl8ny7rg8wmj8nrygx35ds6vcs Issue Tracking, Vendor Advisory, Mailing List
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-16 18:07
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-16 18:07
- CVSS9.1 (v3.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)NVD modified 2026-10-15 17:17
- First seenunscoredNVD modified 2026-10-09 16:33
Affected (CPE criteria) 1
cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*
References 2
- https://lists.apache.org/thread/p1r9t4xl8ny7rg8wmj8nrygx35ds6vcs Issue Tracking, Vendor Advisory, Mailing List
- http://www.openwall.com/lists/oss-security/2026/10/09/4 Mailing List, Third Party Advisory