Skip to content
statance
MenuClose
high · CVSS 8.1

CVE-2026-92857

Keycloak-services: keycloak-services: dcr protocol mapper config not validated, allowing iat holders to forge sub and aud claims in signed tokens

Published 5 Nov 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 10:44 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
keycloak-rhel9-containerRed Hatunaffected: 26.4-29 to < *See vendor advisory
keycloak-rhel9-operator-bundle-containerRed Hatunaffected: 26.4.17-2 to < *See vendor advisory
keycloak-rhel9-operator-containerRed Hatunaffected: 26.4-30 to < *See vendor advisory
keycloak/rhbk-openshift-rhel9Red HatDefault status: unaffectedSee vendor advisory
keycloak-servicesRed HatDefault status: unaffectedSee vendor advisory
rhbk/keycloak-rhel9Red HatDefault status: unaffectedSee vendor advisory
keycloak-servicesRed HatDefault status: unaffectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed