Skip to content

Keycloak 26.8.2 CIMD backchannel_logout_uri causes POST to loopback address #55378

Description

@abstractj

Describe the bug

When the experimental Client ID Metadata Document (CIMD) feature is enabled, the client-id-metadata-document client policy executor does not validate the backchannel_logout_uri value of a client metadata document. The executor validates client_id, redirect_uris, logo_uri, client_uri, tos_uri, policy_uri and jwks_uri, but backchannel_logout_uri is copied into the client configuration as the backchannel logout URL without any check.

As a result, a metadata document served from a hostname accepted by the realm's client policy can set backchannel_logout_uri to a destination that differs from the trusted hostname, such as an HTTP loopback address (for example http://127.0.0.1:19080/capture). This works even when the executor's "Allow http scheme" option is off. When a session for that client is logged out (user-initiated RP logout or admin-initiated logout), Keycloak sends a server-side POST carrying a logout_token to that destination.

Version

26.8.2 with the experimental CIMD feature enabled. Also reproduced on the 999.0.0-SNAPSHOT nightly build of 2026-11-16.

Expected behavior

The backchannel_logout_uri of a CIMD document is validated before the client is stored, with the same scheme and destination rules applied to the other URI fields. The destination is also rechecked when the backchannel request is sent, including redirect handling, so an accepted URL cannot lead the request to a disallowed destination.

Actual behavior

The backchannel_logout_uri is stored as the client's backchannel logout URL without validation. On logout, Keycloak POSTs a logout_token to that URL, including HTTP loopback addresses, regardless of the executor's HTTP scheme setting.

Acknowledgement

Thank you to Dohyun Park (@dhlife09) and the research team (@ye11oc4t, @jiwhan8655, @Dog-Parka) for reporting this issue. As CIMD is an experimental feature, it is not subject to CVEs, so this is handled as a weakness in the public repository.


This issue was originally tracked in the private repository. Migrated by @abstractj.

Activity

  1. added a commit that references this issue on Nov 20, 2026
    690e0d9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for weakness.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions