Live › vulnerability › CVE-2026-117859
Keycloak's Pushed Authorization Request (PAR) handling clears its single-use markers when an authentication flow restarts, while the request stays active. An attacker who holds the same authorization request can reuse it to obtain multiple access tokens.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 07:23 UTC. All times on this page are UTC.
Systems that run Keycloak with the Pushed Authorization Request flow enabled are the ones exposed. The sources do not say which Keycloak versions are affected or whether PAR is on by default, so unknown.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in the Pushed Authorization Request PAR implementation of the keycloak-services component. The issue occurs when an authentication flow is restarted, which incorrectly clears the internal markers used to track PAR consumption while leaving the request active. This allows an attacker to reuse the same authorization request to obtain multiple access tokens, bypassing security requirements for single-use requests.
This page as .md · .json · in your agent: get_signal("CVE-2026-117859")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.