Critical Keycloak Password-Reset Flaw Lets Unauthenticated Attackers Reset Any Account Password

Red Hat and the Keycloak project have issued fixes for a critical vulnerability that can let an unauthenticated remote attacker reset the password for any Keycloak account without ever receiving the emailed reset token. Administrators should treat this as a high-priority update or apply a temporary mitigation recommended by Red Hat.

Key takeaways

  • CVE-2026-18963 is a critical Keycloak password-reset flaw that can let unauthenticated attackers reset any user's password without the emailed token (Red Hat, The Hacker News).
  • Upstream Keycloak users should upgrade to 26.7.2; Red Hat customers must apply the RHBK updates for 26.4.15 and 26.6.6 or follow the vendor's errata (The Hacker News).
  • If immediate patching is impossible, Red Hat's mitigation is to disable the Forgot password option on every realm; still, patching is recommended as soon as possible (Red Hat advisory reporting).
  • Public reporting does not definitively state whether all realm configurations are vulnerable; administrators must follow official advisories for authoritative affected-version lists (The Hacker News, Heise).
  • No evidence of active exploitation was reported at the time of publication, but monitoring and credential rotation are prudent defensive steps (The Hacker News).

What the vulnerability does

Red Hat assigned the vulnerability the identifier CVE-2026-18963 and rated it 9.1 in its CVSS assessment. According to Red Hat’s advisory summarised in reporting by The Hacker News, the issue stems from “improper state validation within the reset-credentials authentication flow.” An attacker can send a crafted request to the reset-credentials endpoint that transitions the authentication session directly into the password-update phase, bypassing the action token that Keycloak normally delivers by email. The result is a full account takeover by setting a new password for any user, including administrative accounts, without the target ever receiving the reset email (reporting based on Red Hat and The Hacker News).

Who is affected and what to install

Keycloak upstream users are advised to upgrade to Keycloak 26.7.2, the release that lists the fix among several security updates, while Red Hat build of Keycloak (RHBK) customers should apply the Red Hat errata that backport fixes for the 26.4 and 26.6 streams. Red Hat published four advisories on August 18, 2026, covering standalone packages and container images for two RHBK streams; the notices reference operator bundles and image tags that identify the patched operator bundles and containers (details summarised from The Hacker News and Red Hat advisories reported there).

Vendor guidance and temporary mitigation

Red Hat has published a temporary mitigation for environments that cannot be updated immediately: disable the “Forgot password” functionality on every realm. The setting is available in the administration console under Realm settings → Login → Forgot password, and must be applied individually for each realm, according to Red Hat’s advisory as reported by The Hacker News. Red Hat emphasised that customers should still upgrade to a fixed version as soon as practical.

Open questions, evidence and scope

Published sources agree the vulnerability allows unauthenticated, network-based attackers to force password resets, but they leave some operational details unresolved. The Keycloak GitHub advisory reportedly lists affected and patched versions as unknown and Red Hat’s CVE record contains only Red Hat product references; public reporting does not definitively state whether every realm configuration that enables forgotten-password is exploitable or only certain reset-credentials flow setups (The Hacker News noted this gap).

Heise reported the same core result and referenced a proof-of-concept repository demonstrating exploitation; Heise also listed the CVSS score as 9.1 and called the issue “critical,” and reiterated that only a username or email address is required to trigger a reset (Heise reporting).

Why this matters for US organisations

Keycloak is widely used as an open-source identity and access management (IAM) server and often protects web applications, API backends and administrative consoles. A successful unauthenticated password reset that impacts administrative users could let an attacker pivot into downstream services that rely on Keycloak for authentication. Reporting cited comments from security researchers in prior Keycloak disclosures that a compromise of Keycloak can expose many resources behind it; while that comment referred to a different vulnerability, it illustrates the systemic risk when an identity provider is breached (The Hacker News).

Immediate actions for administrators

  1. Inventory Keycloak deployments: identify where Keycloak (upstream or RHBK) is used and list version numbers and realms. Prioritise instances exposed to the internet or that protect high-value admin accounts (guidance inferred from vendor mitigation urgency reported by The Hacker News and Heise).
  2. Apply vendor patches: upgrade upstream Keycloak to 26.7.2 or apply the Red Hat updates for RHBK 26.4.15 / 26.6.6 as provided in Red Hat advisories.
  3. If you cannot patch immediately: disable the Forgot password option for every realm in the admin console (Realm settings → Login → Forgot password), as Red Hat recommends.
  4. After patching or mitigation: review authentication logs for unexplained password-reset activity and monitor for abnormal administrative logins. Rotate any credentials for accounts that may have been impacted or show suspicious reset attempts.
  5. Communicate with stakeholders: notify application owners and incident response teams, especially where Keycloak protects administrative access to systems in scope.

The Keycloak 26.7.2 release that lists CVE-2026-18963 among its fixes also addressed a predictable account-linking hash (CVE-2026-15571) and other security issues. Red Hat and Heise coverage show the project has been actively fixing multiple vulnerabilities across recent minor releases; administrators should treat aggregated security patching as part of normal maintenance rather than one-off updates (Heise and The Hacker News reporting).

Remaining uncertainties and follow-ups

At the time of reporting there was no public evidence that the flaw had been exploited in the wild and no independently verified public exploit widely confirmed by multiple vendors. The Keycloak GitHub advisory and some CVE records do not list exact affected versions beyond Red Hat product references, leaving ambiguity about the complete universe of vulnerable deployments. Administrators should follow official Red Hat and Keycloak advisories for authoritative lists and any later clarifications.

Practical checklist (quick)

  • Find Keycloak instances and versions now.
  • Patch to Keycloak 26.7.2 (upstream) or apply RHBK updates for 26.4/26.6 streams.
  • If you cannot patch, disable Forgot password for every realm.
  • Scan logs for reset activity and rotate credentials for at-risk accounts.

“Improper state validation within the reset-credentials authentication flow” — phrase used in Red Hat’s CVE advisory as reported by The Hacker News.

For further details and the official advisories, consult Red Hat’s security errata and the Keycloak 26.7.2 release notes. Zeeshank9.com will update this article if vendors publish additional technical details or revised guidance.

Stay in Touch

spot_img

Related Articles