CVE-2026-7507: Org.keycloak/keycloak-services: session fixation in oidc login flow that can lead to account takeover
A session fixation vulnerability was found in Keycloak's login-actions endpoints. An unauthenticated attacker could exploit this flaw by pre-creating an authentication session and tricking a victim into visiting a maliciously crafted link. By leveraging the /login-actions/restart endpoint—which processes session handles without adequate CSRF protection or cookie ownership validation—an attacker can reset the authentication flow state. This causes Single Sign-On (SSO) to authenticate the victim transparently upon clicking the link, allowing the attacker to hijack the required-action form without needing the victim's credentials. A successful exploit could lead to complete account takeover, including highly privileged administrative accounts.
Security readout for executives and security teams
Plain-English summary
This flaw affects Red Hat build of Keycloak login flows. An attacker could prepare a login session and lure a user to a crafted link, potentially taking over that user’s account after SSO completes. Administrative accounts are in scope if they use the affected flow.
Executive priority
Treat as a high-priority identity platform issue. It can lead to account takeover, including privileged accounts, but current provided evidence does not establish active exploitation.
Technical view
CVE-2026-7507 is a Keycloak session fixation issue in login-actions endpoints, especially /login-actions/restart. The sources describe inadequate CSRF protection and cookie ownership validation for session handles. Exploitation requires network access, no prior authentication, and user interaction, with high impact to confidentiality, integrity, and availability.
Likely exposure
Organizations running Red Hat build of Keycloak 26.2 or 26.4 packages listed as affected are the relevant exposure group. Internet-facing or broadly accessible SSO deployments carry higher business risk.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The described attack requires tricking a victim into visiting a crafted link and depends on the affected OIDC login flow.
Researcher notes
Evidence is strongest for Red Hat build of Keycloak package status and the described session fixation path. Public source details are limited; avoid assuming upstream Keycloak scope beyond the listed Red Hat affected products.
Mitigation direction
Apply the relevant Red Hat RHSA updates for affected Keycloak builds.
Check Red Hat CVE and CSAF VEX guidance for exact fixed package status.
Prioritize patching SSO deployments used by administrators or privileged users.
Review exposure of Keycloak login endpoints while vendor fixes are deployed.
Monitor for suspicious use of /login-actions/restart in authentication logs.
Validation and detection
Inventory Red Hat build of Keycloak 26.2 and 26.4 deployments.
Compare installed packages against the Red Hat affected and unaffected status.
Confirm RHSA-2026:19594 through RHSA-2026:19597 updates are applied where relevant.
Review authentication logs for unusual restart endpoint activity.
Verify privileged accounts cannot be reached through unpatched affected realms.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-290 · source CWE mapping
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.