Description (CNA)
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 (CNA)
| Vendor / product | Versions |
|---|---|
| Red Hat / Red Hat build of Keycloak 26.4 | unaffected 26.4.10-1 before * |
| Red Hat / Red Hat build of Keycloak 26.4 | unaffected 26.4-12 before * |
| Red Hat / Red Hat build of Keycloak 26.4 | unaffected 26.4-12 before * |
| Red Hat / Red Hat build of Keycloak 26.4.10 | unaffected |
| Red Hat / Red Hat Build of Keycloak | affected |
| Red Hat / Red Hat Build of Keycloak | affected |
| Red Hat / Red Hat JBoss Enterprise Application Platform 8 | affected |
| Red Hat / Red Hat JBoss Enterprise Application Platform Expansion Pack | affected |
| Red Hat / Red Hat Single Sign-On 7 | affected |
CWE
CWE-285
References
- https://access.redhat.com/errata/RHSA-2026:3947
- https://access.redhat.com/errata/RHSA-2026:3948
- https://access.redhat.com/security/cve/CVE-2026-2733
- https://bugzilla.redhat.com/show_bug.cgi?id=2440895
ADP enrichment
No English description supplied.
No references supplied.