cve.bz

CVE-2026-4633 redhat build of keycloak

3.7 lowExploit referenceEPSS 0.4%Fix available

Low (3.7) in redhat build of keycloak. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.keycloak:keycloak-services 26.4.12, 26.6.1.

On this page
A flaw was found in Keycloak. A remote attacker can exploit differential error messages during the identity-first login flow when Organizations are enabled. This vulnerability allows an attacker to determine the existence of users, leading to information disclosure through user enumeration.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-209 Generation of Error Message Containing Sensitive Information
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-4633 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-4633?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-4633?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-4633 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.

Badge for a README or a site

CVE-2026-4633

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-4633](https://cve.bz/cve/badge/CVE-2026-4633.svg)](https://cve.bz/cve/CVE-2026-4633)

HTML:

<a href="https://cve.bz/cve/CVE-2026-4633"><img src="https://cve.bz/cve/badge/CVE-2026-4633.svg" alt="CVE-2026-4633"></a>

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rhgq-f8x5-j2jcMavenorg.keycloak:keycloak-services>=26.5.0 <26.6.126.6.1
GHSA-rhgq-f8x5-j2jcMavenorg.keycloak:keycloak-services<26.4.1226.4.12

Red Hat

Red Hat rates this Low.

Red Hat's statement

This flaw has a LOW impact. Keycloak is vulnerable to user enumeration due to differential error messages during the identity-first login flow. Exploitation requires Organizations to be enabled on the realm and the identity-first login flow to be active. This could lead to information disclosure by allowing an attacker to determine the existence of users.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.4.12Fixed 2026-05-20RHSA-2026:19596
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected

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-4633.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-54 Query System for Information Likelihood: High · Severity: Low
  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON