CVE-2026-57818
Race condition lets attackers redeem one auth code to obtain multiple valid access tokens.
Is CVE-2026-57818 being exploited?
Not confirmed. CVE-2026-57818 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-57818?
CVE-2026-57818 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57818?
Yes. A fix has been recorded for CVE-2026-57818. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57818 affect?
CVE-2026-57818 affects JCacheCodeDataProvider, OAuth/OIDC servers using JCacheCodeDataProvider, Versions prior to 4.2.3 / 4.1.8 / 3.6.12. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57818?
Upgrade to 4.2.3, 4.1.8 or 3.6.12 immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Concurrent requests can redeem a single OAuth authorization code multiple times to issue multiple valid access tokens, enabling token reuse and unauthorized access.
Immediate action required
- affected>= 4.2.0 and < 4.2.3
- affected>= 4.0.0 and < 4.1.8
- affected< 3.6.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.