Skip to content
fr Sign in
3.8 Low

CVE-2026-2733 A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even…

Description

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.

Affected products and versions

Product Affected versions Fixed in
Red Hat build of Keycloak 26.4 26.4 earliest → < 26.4-12 26.4-12
Red Hat build of Keycloak 26.4.10 Versions not published
Red Hat Build of Keycloak Versions not published
Red Hat JBoss Enterprise Application Platform 8 Versions not published
Red Hat JBoss Enterprise Application Platform Expansion Pack Versions not published
Red Hat Single Sign-On 7 Versions not published

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Red Hat build of Keycloak 26.4

The 87 CVEs of Red Hat build of Keycloak 26.4 →
CVE-2026-19607 A flaw was found in the first-broker-login flow of the keycloak-services component 5.3 Medium CVE-2026-17526 Keycloak is an open-source identity and access management solution 7.2 High CVE-2026-79651 A flaw was found in the theme localization endpoints of the keycloak-services component, which is the core service… 7.5 High CVE-2026-74909 Keycloak provides a policy enforcer to protect applications by matching incoming web requests against defined security… 8.1 High
Track this CVE