Authorization-code replay via reusable PAR request URIs
Published Sep 23, 2026 · Updated Sep 23, 2026
Authorization bypass in Red Hat build of Keycloak allows remote attackers to reuse a PAR request URI for multiple authorization codes. The prompt=none silent-authentication path skips the consumption step that enforces one-time use of a pushed request URI. Exploitation requires a user with an existing signed-in session, and the resulting impact is repeated authorization-code issuance for that user.
Summary
What happened
Authorization bypass in Red Hat build of Keycloak allows remote attackers to reuse a PAR request URI for multiple authorization codes. The prompt=none silent-authentication path skips the consumption step that enforces one-time use of a pushed request URI. Exploitation requires a user with an existing signed-in session, and the resulting impact is repeated authorization-code issuance for that user.
The record
- CVE
- CVE-2026-96446
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat build of Keycloak
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started