LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
high
Sources
9

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-7507 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9redhat
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-7507Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. ADP timelineredhat-SADP

    Reported to Red Hat.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. ADP timelineredhat-SADP

    Made public.

  5. Source timelineredhat

    Made public.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPorg.keycloak/keycloak-services: Session fixation in OIDC login flow that can lead to account takeover
other:Red Hat severity ratingcvssV3_1
  • 2026-04-30T14:57:56.441Z: Reported to Red Hat.
  • 2026-05-19T10:51:31.418Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-operator-bundle, 26.2.16-1affected
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-rhel9, 26.2-21affected
Red HatRed Hat build of Keycloak 26.2rhbk/keycloak-rhel9-operator, 26.2-21affected
Red HatRed Hat build of Keycloak 26.2.16rhbk/keycloak-rhel9-operatorunaffected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle, 26.4.12-1affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9, 26.4-17affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator, 26.4-17affected
Red HatRed Hat build of Keycloak 26.4.12rhbk/keycloak-rhel9-operatorunaffected
Weakness

CWE details

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.