dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-7507

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 26.4.12 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a session fixation vulnerability in Keycloak's authentication flow where the /login-actions/restart endpoint processes session handles without adequate CSRF protection or cookie ownership validation. An unauthenticated attacker can pre-create an authentication session and trick a victim into clicking a malicious link, causing the SSO to transparently authenticate the victim and allowing the attacker to hijack the required-action form for complete account takeover.

MitigationImplement proper CSRF protection and cookie ownership validation on the /login-actions/restart endpoint to prevent session fixation attacks, and apply any vendor-supplied patches for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:>= 26.4, < 26.4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Keycloak version
    Locate the installed Keycloak version from the server startup logs, the admin console version info, or the version file in the Keycloak installation directory
    Affected if Installed version is greater than or equal to 26.4 but less than 26.4.12
  2. Confirm network exposure of the restart endpoint
    Verify whether your Keycloak server is network-accessible and the /login-actions/restart endpoint is reachable by unauthenticated users
    Affected if The /login-actions/restart endpoint is exposed to unauthenticated network access
  3. Inspect CSRF protection for the restart endpoint
    Review Keycloak security configuration for CSRF token validation on authentication flow endpoints, specifically the /login-actions/restart path
    Affected if CSRF protection is absent or inadequate for the restart endpoint
  4. Check cookie ownership validation
    Examine the authentication session cookie configuration to determine if proper ownership validation is enforced for session handles
    Affected if Cookie ownership validation is not enforced for authentication session handles processed by the restart endpoint

You are affected if your Keycloak version is 26.4 through 26.4.11 and the /login-actions/restart endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 26.4.12 or later
Fixed in 26.4.12
Interim mitigation

Implement proper CSRF protection and cookie ownership validation on the /login-actions/restart endpoint to prevent session fixation attacks, and apply any vendor-supplied patches for this vulnerability.

Recommended fix High confidence

Keycloak 26.4.12 or later

  1. Identify the current Keycloak version using the admin console or CLI (e.g., 'kc.sh version' or checking server logs)
  2. Upgrade Keycloak to version 26.4.12 or later by following the standard upgrade procedure for your deployment method
  3. If using a containerized deployment, update the container image tag to the fixed version (e.g., quay.io/keycloak/keycloak:26.4.12)
  4. Restart the Keycloak server to apply the changes
  5. Verify the upgrade was successful by checking the version output
  6. Test the login flow by attempting to access the /login-actions/restart endpoint to confirm the session fixation protection is in place
  7. Clear any existing browser sessions and test a full login sequence to ensure SSO functions correctly post-upgrade
Caveat Patch release with security fixes; minimal risk but should be tested in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7507 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data