A flaw was found in the user-event metrics recording of Keycloak. (CVE-2026-16100)
A vulnerability in Keycloak's user-event metrics recording allows an authenticated user with specific account management permissions to cause a denial of service. When metrics are enabled, raw error messages from failed account operations, which can include user-supplied input, are recorded as Prometheus metric labels. This can lead to unbounded metric cardinality, exhausting system memory and causing the service to crash or become unavailable.
AI Analysis
Technical Summary
CVE-2026-16100 is a vulnerability in Keycloak where the user-event metrics system records raw error messages from failed account operations as Prometheus metric labels. Because these error messages may contain user-controlled input such as nonexistent client IDs, an authenticated user with account management permissions can generate a large number of unique metric entries. This unbounded metric cardinality can exhaust system memory, leading to denial of service by crashing or making the service unavailable. The vulnerability arises from the use of unsanitized, request-controlled input within Prometheus metric labels. The Red Hat Product Security team assessed this vulnerability as Moderate severity with a CVSS 3.1 base score of 6.5, noting that exploitation requires authenticated access with specific permissions. No official fix or patch is currently available according to the Red Hat advisory, and mitigation options are limited or do not meet criteria for ease of use or applicability.
Potential Impact
Successful exploitation allows an authenticated user with specific account management permissions to cause a denial of service by exhausting system memory. This results in the Keycloak service crashing or becoming unavailable. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
According to the Red Hat advisory, no mitigation or official fix is currently available that meets criteria for ease of use, deployment, or applicability. Users should monitor vendor advisories for updates. Since exploitation requires authenticated access with specific permissions, restricting such access may reduce risk. Consider disabling metrics if feasible until a fix is available.
A flaw was found in the user-event metrics recording of Keycloak. (CVE-2026-16100)
Description
A vulnerability in Keycloak's user-event metrics recording allows an authenticated user with specific account management permissions to cause a denial of service. When metrics are enabled, raw error messages from failed account operations, which can include user-supplied input, are recorded as Prometheus metric labels. This can lead to unbounded metric cardinality, exhausting system memory and causing the service to crash or become unavailable.
CVSS v3.1
Score 6.5medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16100 is a vulnerability in Keycloak where the user-event metrics system records raw error messages from failed account operations as Prometheus metric labels. Because these error messages may contain user-controlled input such as nonexistent client IDs, an authenticated user with account management permissions can generate a large number of unique metric entries. This unbounded metric cardinality can exhaust system memory, leading to denial of service by crashing or making the service unavailable. The vulnerability arises from the use of unsanitized, request-controlled input within Prometheus metric labels. The Red Hat Product Security team assessed this vulnerability as Moderate severity with a CVSS 3.1 base score of 6.5, noting that exploitation requires authenticated access with specific permissions. No official fix or patch is currently available according to the Red Hat advisory, and mitigation options are limited or do not meet criteria for ease of use or applicability.
Potential Impact
Successful exploitation allows an authenticated user with specific account management permissions to cause a denial of service by exhausting system memory. This results in the Keycloak service crashing or becoming unavailable. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
According to the Red Hat advisory, no mitigation or official fix is currently available that meets criteria for ease of use, deployment, or applicability. Users should monitor vendor advisories for updates. Since exploitation requires authenticated access with specific permissions, restricting such access may reduce risk. Consider disabling metrics if feasible until a fix is available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xj3w-m54w-h7p9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-16100"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a738521bf8831d5394efa4a
Added to database: 08/05/2026, 18:46:57 UTC
Last enriched: 08/05/2026, 22:17:09 UTC
Last updated: 08/06/2026, 03:40:59 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.