Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4gv3-mc9p-5wqc

Keycloak: Unauthenticated account takeover via reset-credentials flow bypass

CVSS 9.1 CriticalCriticalEPSS 0.047 · 91st percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 18 Aug 2026, 18:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven>=26.0.0, <26.4.15 || >=26.5.0, <26.6.6 || >=26.7.0, <26.7.226.4.15, 26.6.6, 26.7.2
Identifiers
GHSA-4gv3-mc9p-5wqc · BIT-keycloak-2026-18963 · CVE-2026-18963
Weakness (CWE)
CWE-640
Tags
Published
18 Aug 2026
Updated
28 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Keycloak's keycloak-services package is vulnerable in versions 26.0.0 up to 26.4.15, 26.5.0 up to 26.6.6, and 26.7.0 up to 26.7.2. An unauthenticated attacker can bypass the email verification step of the reset-credentials flow and set new credentials for any user, gaining full control of that account. Upgrade to version 26.4.15, 26.6.6, or 26.7.2, depending on your release line.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.047, the 91st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.