CVE-2026-2733
Low · 3.8CVSS
3.8
EPSS
0.5%
Published
Feb 19, 2026
CISA due date
—
The record
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 packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Maven | org.keycloak:keycloak-services | 0 | No fix |
Related vulnerabilities
- GHSA-fjf4-6f34-w64q Keycloak: Missing Check on Disabled Client for Docker Registry Protocol Same vulnerability
- GHSA-7g5x-9c4v-4w5r Keycloak REST Services has a WebAuthn Attestation Statement Verification Bypass Also affects org.keycloak:keycloak-services
- CVE-2025-12150 A flaw was found in Keycloak’s WebAuthn registration component. Also affects org.keycloak:keycloak-services
- GHSA-37gf-gmxv-74wv Keycloak fails to verify if an Identity Provider (IdP) is enabled before issuing tokens Also affects org.keycloak:keycloak-services
- GHSA-hcvw-475w-8g7p Keycloak affected by improper invitation token validation Also affects org.keycloak:keycloak-services
- GHSA-fm6w-rrp3-2x4w Keycloak Affected by Broken Access Control Vulnerability in the… Also affects org.keycloak:keycloak-services
- CVE-2026-1486 A flaw was found in Keycloak. Also affects org.keycloak:keycloak-services
- CVE-2026-1529 A flaw was found in Keycloak. Also affects org.keycloak:keycloak-services