Loading vulnerability…
CVE-2026-1035 is a race condition in Keycloak refresh token processing. The flaw is in the TokenManager logic that enforces refresh token reuse policy when strict refresh token rotation is enabled. Validation of whether a refresh token has already been used and the subsequent state update marking that token as consumed are not performed atomically. An attacker who can submit concurrent refresh requests using the same valid refresh token can exploit this time-of-check time-of-use condition to bypass single-use enforcement and obtain multiple access tokens from one refresh token. The issue undermines the security guarantees of refresh token rotation hardening in affected Keycloak deployments.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Keycloak flaw allowing refresh token reuse bypass through a time-of-check/time-of-use race condition.
A CVE identifier cited as an example of traditional CVE entries ingested/aggregated by the EU Vulnerability Database (GCVE).
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.