Keycloak Fixes Unauthenticated Password-Reset Account Takeover

P1 — VALIDATE AND UPDATECritical · 9.1 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Identify affected Keycloak service versions, install the fixed release for the deployed branch, and review unexpected password resets or account changes.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Keycloak versions, realm recovery flows, deployment replicas, dependent applications and identity-service owners. Match the three owner-stated version ranges. Evaluate exposed password-reset paths without using a live account-takeover test. Upgrade the affected branch to its listed fixed release through the supported deployment procedure and validate every replica. Test legitimate recovery and email-verification behavior, review suspicious credential changes and administrative events, and retain rollout and investigation evidence.

Open the authoritative advisory

Last verified: 2026-11-20 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeorg.keycloak:keycloak-services reset-credentials flow
AdvisoryGHSA-6qm4-x97f-55fh
CVECVE-2026-18963
Authoritative release date2026-11-19T19:08:46Z — repository-owner security-advisory API.
Authority revision dateNo separate material revision is stated for this release.
Affected versions26.0.0 through versions before 26.4.15; 26.5.0 through versions before 26.6.6; and 26.7.0 through versions before 26.7.2.
Fixed versionBranch-specific fixed releases: 26.4.15, 26.6.6 and 26.7.2.
CVSS base score9.1 (CVSS v3.1)
CVSS severityCritical
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

The project disclosed a password-reset flow bypass that can let an unauthenticated attacker set a user’s credentials without completing the email verification link.

What To Validate Now

  1. Inventory. Record Keycloak versions, realm recovery flows, deployment replicas, dependent applications and identity-service owners.
  2. Establish applicability. Match the three owner-stated version ranges. Evaluate exposed password-reset paths without using a live account-takeover test.
  3. Remediate. Upgrade the affected branch to its listed fixed release through the supported deployment procedure and validate every replica.
  4. Validate. Test legitimate recovery and email-verification behavior, review suspicious credential changes and administrative events, and retain rollout and investigation evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Coordinate identity-service changes with relying applications and recovery administrators. The advisory does not confirm exploitation or supply a compensating workaround.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.