CVE-2025-12390: Session Fixation in Red Hat Red Hat Build of Keycloak
A flaw was found in Keycloak. In Keycloak where a user can accidentally get access to another user's session if both use the same device and browser. This happens because Keycloak sometimes reuses session identifiers and doesn’t clean up properly during logout when browser cookies are missing. As a result, one user may receive tokens that belong to another user.
AI Analysis
Technical Summary
CVE-2025-12390 is a session fixation vulnerability identified in the Red Hat Build of Keycloak, an open-source identity and access management solution widely used for single sign-on and authentication services. The flaw arises because Keycloak sometimes reuses session identifiers and fails to properly clean up sessions during logout when browser cookies are missing. This improper session management can lead to a scenario where two different users sharing the same device and browser may inadvertently share session tokens, allowing one user to gain unauthorized access to another user's session. The vulnerability requires that both users operate on the same device/browser environment, and that the logout process does not clear session identifiers correctly due to missing cookies. The CVSS 3.1 vector indicates local attack vector (AV:L), high attack complexity (AC:H), low privileges required (PR:L), and user interaction required (UI:R). The impact on confidentiality and integrity is high because session tokens can be exposed and misused, but availability is not affected. No known exploits have been reported in the wild, and no patches have been linked yet, though Red Hat is expected to release fixes. This vulnerability highlights the importance of robust session management and cookie handling in authentication systems to prevent session fixation and unauthorized access.
Potential Impact
For European organizations, especially those relying on Red Hat Build of Keycloak for identity and access management, this vulnerability poses a significant risk to user session confidentiality and integrity. Unauthorized access to user sessions could lead to data breaches, privilege escalation, and unauthorized actions performed under another user's identity. This is particularly critical in environments where devices are shared among multiple users, such as public terminals, call centers, or shared workstations. The risk is amplified in sectors handling sensitive personal data or critical infrastructure, including government agencies, financial institutions, and healthcare providers. Although exploitation requires local access and user interaction, the potential for insider threats or social engineering attacks exploiting this flaw is notable. The absence of proper session invalidation could undermine trust in authentication mechanisms and complicate compliance with GDPR and other data protection regulations.
Mitigation Recommendations
Organizations should proactively monitor for updates and patches from Red Hat addressing this vulnerability and apply them promptly once available. In the interim, administrators should enforce strict session management policies, including ensuring that logout processes fully invalidate sessions and clear all session identifiers regardless of cookie presence. Implementing additional controls such as device fingerprinting or multi-factor authentication can reduce the risk of session misuse. Educate users about the risks of shared device usage and encourage practices such as closing browsers completely after logout. Where possible, restrict shared device usage or implement session timeout policies to minimize exposure. Conduct regular security audits and penetration testing focused on session management to detect similar issues. Finally, review and enhance cookie security settings, including setting the HttpOnly and Secure flags, to prevent session token leakage.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain
CVE-2025-12390: Session Fixation in Red Hat Red Hat Build of Keycloak
Description
A flaw was found in Keycloak. In Keycloak where a user can accidentally get access to another user's session if both use the same device and browser. This happens because Keycloak sometimes reuses session identifiers and doesn’t clean up properly during logout when browser cookies are missing. As a result, one user may receive tokens that belong to another user.
AI-Powered Analysis
Technical Analysis
CVE-2025-12390 is a session fixation vulnerability identified in the Red Hat Build of Keycloak, an open-source identity and access management solution widely used for single sign-on and authentication services. The flaw arises because Keycloak sometimes reuses session identifiers and fails to properly clean up sessions during logout when browser cookies are missing. This improper session management can lead to a scenario where two different users sharing the same device and browser may inadvertently share session tokens, allowing one user to gain unauthorized access to another user's session. The vulnerability requires that both users operate on the same device/browser environment, and that the logout process does not clear session identifiers correctly due to missing cookies. The CVSS 3.1 vector indicates local attack vector (AV:L), high attack complexity (AC:H), low privileges required (PR:L), and user interaction required (UI:R). The impact on confidentiality and integrity is high because session tokens can be exposed and misused, but availability is not affected. No known exploits have been reported in the wild, and no patches have been linked yet, though Red Hat is expected to release fixes. This vulnerability highlights the importance of robust session management and cookie handling in authentication systems to prevent session fixation and unauthorized access.
Potential Impact
For European organizations, especially those relying on Red Hat Build of Keycloak for identity and access management, this vulnerability poses a significant risk to user session confidentiality and integrity. Unauthorized access to user sessions could lead to data breaches, privilege escalation, and unauthorized actions performed under another user's identity. This is particularly critical in environments where devices are shared among multiple users, such as public terminals, call centers, or shared workstations. The risk is amplified in sectors handling sensitive personal data or critical infrastructure, including government agencies, financial institutions, and healthcare providers. Although exploitation requires local access and user interaction, the potential for insider threats or social engineering attacks exploiting this flaw is notable. The absence of proper session invalidation could undermine trust in authentication mechanisms and complicate compliance with GDPR and other data protection regulations.
Mitigation Recommendations
Organizations should proactively monitor for updates and patches from Red Hat addressing this vulnerability and apply them promptly once available. In the interim, administrators should enforce strict session management policies, including ensuring that logout processes fully invalidate sessions and clear all session identifiers regardless of cookie presence. Implementing additional controls such as device fingerprinting or multi-factor authentication can reduce the risk of session misuse. Educate users about the risks of shared device usage and encourage practices such as closing browsers completely after logout. Where possible, restrict shared device usage or implement session timeout policies to minimize exposure. Conduct regular security audits and penetration testing focused on session management to detect similar issues. Finally, review and enhance cookie security settings, including setting the HttpOnly and Secure flags, to prevent session token leakage.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- redhat
- Date Reserved
- 2025-10-28T13:14:38.975Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6900c82a05cd0025c8e834e4
Added to database: 10/28/2025, 1:42:02 PM
Last enriched: 10/28/2025, 1:52:08 PM
Last updated: 10/28/2025, 10:29:16 PM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-64095: CWE-434: Unrestricted Upload of File with Dangerous Type in dnnsoftware Dnn.Platform
CriticalCVE-2025-64094: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in dnnsoftware Dnn.Platform
MediumCVE-2025-62800: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in jlowin fastmcp
MediumCVE-2025-62802: CWE-1188: Insecure Default Initialization of Resource in dnnsoftware Dnn.Platform
MediumCVE-2025-62801: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in jlowin fastmcp
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.