Keycloak does not invalidate offline sessions when the offline_access scope is removed
Published Oct 23, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Keycloak does not invalidate offline sessions when the offline_access scope is removed
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A flaw was found in Keycloak. An offline session continues to be valid when the offline_access scope is removed from the client. The refresh token is accepted and you can continue to request new tokens for the session. As it can lead to a situation where an administrator removes the scope, and assumes that offline sessions are no longer available, but they are.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2025:21370 ↗
- RHSA-2025:21371 ↗
- RHSA-2025:22088 ↗
- RHSA-2025:22089 ↗
- access.redhat.com ↗
- RHBZ#2406033 ↗
- Source repository ↗
Record history
Published Oct 23, 2025 · Last refreshed Nov 3, 2026