CVSS 3.1
9.1 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCritical (9.1) in red hat. EPSS 8.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.keycloak:keycloak-services 26.4.15, 26.6.6, 26.7.2.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Norg.keycloak:keycloak-services (Maven): fixed in 26.4.15, 26.6.6, 26.7.2Explain CVE-2026-18963 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18963?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18963?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18963 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat build of Keycloak 26.4 | 26.4.15-1 |
| Red Hat build of Keycloak 26.4 | 26.4-23 |
| Red Hat build of Keycloak 26.6 | 26.6.6-1 |
| Red Hat build of Keycloak 26.6 | 26.6-12 |
| Red Hat Single Sign-On 7.6 for RHEL 7 | 0:18.0.21-1.redhat_00001.1.el7sso |
| Red Hat Single Sign-On 7.6 for RHEL 8 | 0:18.0.21-1.redhat_00001.1.el8sso |
| Red Hat Single Sign-On 7.6 for RHEL 9 | 0:18.0.21-1.redhat_00001.1.el9sso |
| Red Hat RHEL-8 based Middleware Containers | 7.6-88 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-4gv3-mc9p-5wqc | Maven | org.keycloak:keycloak-services | >=26.0.0 <26.4.15 | 26.4.15 |
| GHSA-4gv3-mc9p-5wqc | Maven | org.keycloak:keycloak-services | >=26.5.0 <26.6.6 | 26.6.6 |
| GHSA-4gv3-mc9p-5wqc | Maven | org.keycloak:keycloak-services | >=26.7.0 <26.7.2 | 26.7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | red_hat_single_sign_on:7.6::el7 | rh-sso7-keycloak, rh-sso7-keycloak-server | 0:18.0.21-1.redhat_00001.1.el7sso | RHSA-2026:99764 |
| Red Hat | red_hat_single_sign_on:7.6::el8 | rh-sso7-keycloak, rh-sso7-keycloak-server | 0:18.0.21-1.redhat_00001.1.el8sso | RHSA-2026:99765 |
| Red Hat | red_hat_single_sign_on:7.6::el9 | rh-sso7-keycloak, rh-sso7-keycloak-server | 0:18.0.21-1.redhat_00001.1.el9sso | RHSA-2026:99766 |
From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.
Red Hat rates this Critical.
The Red Hat Product Security team has assessed the severity of this vulnerability as Critical, given that it can be exploited by an unauthenticated remote attacker without any user interaction. Successful exploitation allows an attacker to gain full access to any user account by bypassing the email verification step in the password recovery process. The vulnerability's root cause is improper state validation within the reset-credentials authentication flow.
If an immediate upgrade is not possible, disabling the "Forgot password" functionality across all realms can be used as a temporary mitigation.
In the RHBK administration console, navigate to:
Realm settings → Login → Forgot password → Off
Apply this setting to all realms.
Upgrade to a fixed version as soon as possible.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-operator-bundle:26.4.15-1 | Fixed 2026-08-18 | RHSA-2026:56519 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9:26.4-23 | Fixed 2026-08-18 | RHSA-2026:56519 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9-operator:26.4-23 | Fixed 2026-08-18 | RHSA-2026:56519 |
| Red Hat build of Keycloak 26.4.15 | keycloak-services | Fixed 2026-08-18 | RHSA-2026:56520 |
| Red Hat build of Keycloak 26.4.15 | rhbk-openshift-rhel9/rhbk-openshift-rhel9 | Fixed 2026-08-18 | RHSA-2026:56520 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-operator-bundle:26.6.6-1 | Fixed 2026-08-18 | RHSA-2026:56524 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-rhel9:26.6-12 | Fixed 2026-08-18 | RHSA-2026:56524 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-rhel9-operator:26.6-12 | Fixed 2026-08-18 | RHSA-2026:56524 |
| Red Hat build of Keycloak 26.6.6 | keycloak-services | Fixed 2026-08-18 | RHSA-2026:56523 |
| Red Hat build of Keycloak 26.6.6 | rhbk-keycloak-rhel9/rhbk-keycloak-rhel9 | Fixed 2026-08-18 | RHSA-2026:56523 |
| Red Hat build of Keycloak 26.6.6 | rhbk-openshift-rhel9/rhbk-openshift-rhel9 | Fixed 2026-08-18 | RHSA-2026:56523 |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | keycloak-services | Not affected | |
| Red Hat Single Sign-On 7 | keycloak-services | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-18963.
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-26-265-06 | Siemens Industrial Edge Management | 2026-09-08 | Critical Manufacturing | Industrial Edge Management Cloud, Industrial Edge Management Pro V1 >= V1.14.9 < V1.15.20, Industrial Edge Management Pro V2 >= V2.2.0 < V2.2.2 and 1 more | none listed |
From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.