CVE-2026-2733: Keycloak: Missing Check on Disabled Client for Docker Registry Protocol
(updated )
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.
References
- access.redhat.com/errata/RHSA-2026:3947
- access.redhat.com/errata/RHSA-2026:3948
- access.redhat.com/security/cve/CVE-2026-2733
- bugzilla.redhat.com/show_bug.cgi?id=2440895
- github.com/advisories/GHSA-fjf4-6f34-w64q
- github.com/keycloak/keycloak
- github.com/keycloak/keycloak/commit/743ac24081b2c6da36aac3775147ec5b80c2861e
- github.com/keycloak/keycloak/issues/46462
- nvd.nist.gov/vuln/detail/CVE-2026-2733
Code Behaviors & Features
Detect and mitigate CVE-2026-2733 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →