cve.bz

CVE-2026-96460

5.4 mediumEPSS 0.2%Fix available

Medium (5.4) in red hat. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in the token exchange mechanism of Keycloak. When using Standard Token Exchange V2, the system issues new tokens with a fresh lifetime based on the requester clients configuration instead of limiting it to the original tokens expiration. This issue allows an authenticated requester to indefinitely extend access for service accounts by repeatedly exchanging tokens, even if the original client has been disabled by an administrator.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-303 Incorrect Implementation of Authentication Algorithm
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-96460 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96460?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96460?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96460 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:red hat build of keycloak 26.6
  • red hat:red hat build of keycloak 26.6.8
  • red hat:red hat single sign-on 7

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.626.6.8-2
Red Hat build of Keycloak 26.626.6-24

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to already possess a valid exchanged service-account token and the credentials of an authorized requester client. Successful exploitation allows an attacker to maintain persistent access to resources indefinitely, bypassing administrative revocation of the origin client. The vulnerability's root cause is the failure to bound exchanged token lifetimes by the original subject token's expiration.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.8-2Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6.8keycloak-servicesFixed 2026-11-06RHSA-2026:95761
Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9Fixed 2026-11-06RHSA-2026:95761
Red Hat Single Sign-On 7keycloak-servicesNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-96460.

Attack patterns (CAPEC)

  • CAPEC-90 Reflection Attack in Authentication Protocol Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON