Skip to main content

CVE-2026-73179: CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition in Apache Software Foundation Apache CXF

0
High
VulnerabilityCVE-2026-73179cvecve-2026-73179cwe-367
Published: 10/09/2026 (10/09/2026, 10:17:41 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache CXF

Description

Improper enforcement of single-use authorization code semantics in the JPA OAuth2 authorization code grant provider in Apache CXFallows a remote attacker to obtain multiple valid access tokens from a single authorization code via concurrent token exchange requests that race the non-atomic find-then-delete operation against a shared relational database under READ_COMMITTED isolation. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fixes this issue.

Affected software

Apache Software Foundation

Apache CXF

Affected versions
>=4.2.0 <4.2.4>=4.0.0 <4.1.9>=0 <3.6.13
Apache Software Foundation/org.apache.cxf:cxf-rt-rs-security-oauth2
pkg:maven/Apache Software Foundation/org.apache.cxf:cxf-rt-rs-security-oauth2
Affected versions
>=4.2.0 <4.2.4>=4.0.0 <4.1.9>=0 <3.6.13

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/09/2026, 10:49:18 UTC

Technical Analysis

The vulnerability arises from improper enforcement of single-use authorization code semantics in the JPA OAuth2 authorization code grant provider within Apache CXF. Under READ_COMMITTED isolation, concurrent token exchange requests can race the non-atomic find-then-delete operation against a shared relational database, enabling an attacker to reuse a single authorization code to obtain multiple valid access tokens. This is a classic TOCTOU race condition (CWE-367). The issue is resolved in Apache CXF versions 4.2.4, 4.1.9, and 3.6.13.

Potential Impact

An attacker can exploit this race condition to obtain multiple valid access tokens from a single authorization code, potentially leading to unauthorized access to protected resources. This undermines the intended single-use nature of authorization codes in OAuth2 flows, increasing the risk of token replay and unauthorized resource access.

Mitigation Recommendations

Users should upgrade Apache CXF to versions 4.2.4, 4.1.9, or 3.6.13 or later, where this race condition has been fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-08-11T10:44:12.783Z
State
PUBLISHED

Threat ID: 6ac8c31f2cdf04f6564c0cd7

Added to database: 10/09/2026, 10:34:07 UTC

Last enriched: 10/09/2026, 10:49:18 UTC

Last updated: 10/09/2026, 18:57:32 UTC

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses