Access-token theft via unbound authorization codes
Published Jul 17, 2026 · Updated Jul 17, 2026
Authorization-code binding failure in Red Hat build of Keycloak allows remote authenticated users to obtain victim access tokens. The keycloak-services authorization-code payload omits the issuing client identifier, so redemption accepts a code retargeted to another client session. Exploitation requires interception of a valid code, a registered client in the same realm, and victim interaction; it exposes the victim's identity tokens.
Summary
What happened
Authorization-code binding failure in Red Hat build of Keycloak allows remote authenticated users to obtain victim access tokens. The keycloak-services authorization-code payload omits the issuing client identifier, so redemption accepts a code retargeted to another client session. Exploitation requires interception of a valid code, a registered client in the same realm, and victim interaction; it exposes the victim's identity tokens.
The record
- CVE
- CVE-2026-16089
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-384, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 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
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo