# CVE-2026-18963: Keycloak-services: keycloak-services: unauthenticated account takeover via reset-credentials flow bypass > Unauthenticated attackers can bypass email verification in the password reset flow to take over any user account in Keycloak. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Aug 2026 - **Updated:** 23 Oct 2026 - **Also known as:** BIT-keycloak-2026-18963, GHSA-4gv3-mc9p-5wqc, MINI-8p5h-fpq7-v4fq, MINI-frxh-pvqr-j73f ## What is CVE-2026-18963? CVE-2026-18963 is a critical authentication bypass vulnerability in Red Hat JBoss Enterprise Application Platform Expansion Pack, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in the reset-credentials flow of the keycloak-services component, which is the core engine for identity and access management in Red Hat Build of Keycloak. The issue allows an unauthenticated attacker to force the password reset process for any user without needing to click the required email verification link. This can result in the attacker gaining full control over target user accounts by directly setting new credentials. Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password) ## Which versions are affected by CVE-2026-18963? 7 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.keycloak:keycloak-services` | Maven | From 26.0.0 | 26.4.15 | | `org.keycloak:keycloak-services` | Maven | From 26.0.0 | 26.4.15 | | `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.6.6 | | `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.6.6 | | `org.keycloak:keycloak-services` | Maven | From 26.7.0 | 26.7.2 | | `org.keycloak:keycloak-services` | Maven | From 26.7.0 | 26.7.2 | | `keycloak` | Bitnami | All versions | 26.7.2 | ## How do I fix CVE-2026-18963? Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.4.15, 26.6.6 or 26.7.2. ## Is CVE-2026-18963 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18963 exists. Public exploit code: - **CVE-2026-18963** — unauthenticated Keycloak account takeover via the reset-credentials flow. (github_poc): https://github.com/ynsmroztas/KeySniper - Exploit for KeyCloak CVE-2026-18963 (github_poc): https://github.com/Snizi/CVE-2026-18963-Exploit - CVE-2026-18963 (github_poc): https://github.com/Red-Darkin/CVE-2026-18963-keycloak - Keycloak reset-credentials flow bypass (github_poc): https://github.com/EQSTLab/CVE-2026-18963 - This repo is poc of cve-2026-18963. Please use it on legal products (lab, local,...). (github_poc): https://github.com/prot0tw/Keycloak_CVE-2026-18963_PoC - Hunt for CVE-2026-18963 exploitation traces (Keycloak unauthenticated account takeover) in the Keycloak database (github_poc): https://github.com/kyos-public/keycloak-cve-2026-18963-hunt ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-18963 and fix it if it is affected. What it is: CVE-2026-18963 is a critical authentication bypass vulnerability in Red Hat JBoss Enterprise Application Platform Expansion Pack, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18963 exists. Affected packages and fixed versions: - org.keycloak:keycloak-services (Maven): affected from 26.0.0; fixed in 26.4.15 - org.keycloak:keycloak-services (Maven): affected from 26.0.0; fixed in 26.4.15 - org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.6.6 - org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.6.6 - org.keycloak:keycloak-services (Maven): affected from 26.7.0; fixed in 26.7.2 - org.keycloak:keycloak-services (Maven): affected from 26.7.0; fixed in 26.7.2 - keycloak (Bitnami): affected all versions; fixed in 26.7.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-18963/ (Markdown: https://insights.sbomify.com/CVE-2026-18963/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18963 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18963 - OSV: https://osv.dev/vulnerability/CVE-2026-18963 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-18963/ Summaries are generated and may contain mistakes; the official description above is the record.