How severe is CVE-2026-9802?

CVE-2026-9802 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-9802 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-9802?

CVE-2026-9802 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-9802?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-9802 have an EU (EUVD) identifier?

Yes. CVE-2026-9802 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32720.

When was CVE-2026-9802 published?

CVE-2026-9802 was published on 2026-05-28 and last updated on 2026-06-26.

CVE-2026-9802

CVE-2026-9802 is a medium-severity vulnerability in Redhat Build Of Keycloak with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-613.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (22nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-32720
Weakness: CWE-613
Affected product: Redhat Build Of Keycloak
Published: 2026-05-28
Last modified: 2026-06-26

Description

A flaw was found in Keycloak. When revokeRefreshToken=true is enabled and persistent session storage is in use, a server restart can reset internal timing mechanisms. This allows a remote attacker, who has previously captured a user's refresh token, to replay that token even after it has been revoked. Successful exploitation grants the attacker unauthorized access to the victim's account, potentially leading to information disclosure or privilege escalation.

Frequently asked questions

What is CVE-2026-9802?: A flaw was found in Keycloak. When revokeRefreshToken=true is enabled and persistent session storage is in use, a server restart can reset internal timing mechanisms. This allows a remote attacker, who has previously captured a user's refresh token, to replay that token even after it has been revoked. Successful exploitation grants the attacker unauthorized access to the victim's account, potentially leading to information disclosure or privilege escalation.
How severe is CVE-2026-9802?: CVE-2026-9802 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-9802 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-9802?: CVE-2026-9802 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-9802?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-9802 have an EU (EUVD) identifier?: Yes. CVE-2026-9802 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32720.
When was CVE-2026-9802 published?: CVE-2026-9802 was published on 2026-05-28 and last updated on 2026-06-26.

References

Affected products (1)

cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*

More vulnerabilities in Redhat Build Of Keycloak

CVE-2026-3047 — High (CVSS 8.8): A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is…
CVE-2026-11800 — High (CVSS 8.1): A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an…
CVE-2026-9800 — High (CVSS 8.1): A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all…
CVE-2026-7504 — High (CVSS 8.1): A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an…
CVE-2026-4636 — High (CVSS 8.1): A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA)…
CVE-2026-3009 — High (CVSS 8.1): A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using…

All CVEs affecting Redhat Build Of Keycloak →

Other CWE-613 (Insufficient Session Expiration) vulnerabilities

CVE-2024-8888 — Critical (CVSS 10.0): An attacker with access to the network where CIRCUTOR Q-SMT is located in its firmware version 1.0.4, could steal the…
CVE-2026-46455 — Critical (CVSS 9.8): Insufficient Session Expiration vulnerability in Apache Camel Keycloak Component. The camel-keycloak security helper…
CVE-2026-21622 — Critical (CVSS 9.8): Insufficient Session Expiration vulnerability in hexpm hexpm/hexpm ('Elixir.Hexpm.Accounts.PasswordReset' module)…
CVE-2025-59786 — Critical (CVSS 9.8): 2N Access Commander version 3.4.2 and prior improperly invalidates session tokens, allowing multiple session cookies to…
CVE-2026-26342 — Critical (CVSS 9.8): Tattile Smart+, Vega, and Basic device families firmware versions 1.181.5 and prior implement an authentication token…
CVE-2026-1435 — Critical (CVSS 9.8): Not properly invalidated session vulnerability in Graylog Web Interface, version 2.2.3, due to incorrect management of…

Browse all CWE-613 (Insufficient Session Expiration) vulnerabilities →