CVE-2026-57818
Received Received - Intake

Race Condition in JCacheCodeDataProvider Leads to Token Reuse

Publication date: 2026-08-06

Last updated on: 2026-08-06

Assigner: Apache Software Foundation

Description
A race condition in JCacheCodeDataProvider allows an attacker to redeem a single authorization code multiple times via concurrent requests, resulting in the issuance of multiple distinct, valid access tokens. Users are recommended to upgrade to versions 4.2.3, 4.1.8 or 3.6.12, which fix this issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-06
Last Modified
2026-08-06
Generated
2026-08-06
AI Q&A
2026-08-06
EPSS Evaluated
N/A
NVD
CVE-2026-57818
EUVD
EUVD-2026-53862

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
apache jcache 4.2.3
apache jcache 4.1.8
apache jcache 3.6.12

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in JCacheCodeDataProvider that lets an attacker redeem a single authorization code multiple times through concurrent requests. This results in the issuance of multiple valid access tokens from one code.

Detection Guidance

Detecting this vulnerability requires checking the version of Apache JCache. Run commands like 'find / -name "jcache*.jar" 2>/dev/null' to locate JCache files, then inspect version details in the file or via 'java -jar <jcache-jar> --version'. Compare the version against 4.2.3, 4.1.8, or 3.6.12 to determine exposure.

Impact Analysis

An attacker could exploit this to gain unauthorized access to user accounts or services by obtaining multiple access tokens from a single authorization code. This could lead to data breaches or unauthorized actions on behalf of legitimate users.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements. It may result in non-compliance, legal penalties, or reputational damage due to compromised user data.

Mitigation Strategies

Upgrade Apache JCache to a fixed version (4.2.3, 4.1.8, or 3.6.12) immediately. If upgrading is not possible, restrict concurrent requests to the authorization endpoint or implement rate limiting to prevent abuse of the race condition.

Chat Assistant

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

EPSS Chart