CVE-2026-57818 is a race condition in the Apache CXF OAuth2 component org.apache.cxf:cxf-rt-rs-security-oauth2, specifically in JCacheCodeDataProvider. The flaw allows a single OAuth2 authorization code to be redeemed multiple times when concurrent token requests are submitted before the code is invalidated or otherwise marked as consumed. This breaks the intended single-use property of the OAuth2 authorization code flow and results in the server issuing multiple distinct valid access tokens derived from the same authorization code. The issue has been described as an authorization code replay condition caused by a time-of-check to time-of-use weakness in code redemption handling.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.