Keycloak: Missing Check on Disabled Client for Docker Registry Protocol
A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously valid credentials can still be used to obtain authentication tokens. This weakens administrative controls and could allow unintended access to container registry resources.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-2733US | — | — | ||
A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disable… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:3947WEB
- https://access.redhat.com/errata/RHSA-2026:3948WEB
- https://access.redhat.com/security/cve/CVE-2026-2733WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2440895WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/commit/743ac24081b2c6da36aac3775147ec5b80c2861eWEB
- https://github.com/keycloak/keycloak/issues/46462WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-2733ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan