Skip to content
OpenAdvisories

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

VendorProductAffectedFixed
Red Hat Red Hat build of Keycloak 26.4 — —
Red Hat Red Hat build of Keycloak 26.4.10 — —
Red Hat Red Hat Build of Keycloak — —
Red Hat Red Hat JBoss Enterprise Application Platform 8 — —
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack — —
Red Hat Red Hat Single Sign-On 7 — —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling keycloak-26.4-iamguarded-compat No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
Maven org.keycloak:keycloak-services <= 26.5.3 — GHSA-fjf4-6f34-w64q

Advisories 1

References