CVE-2026-2733
A flaw was identified in the Docker v2 authentication endpoint of …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-2733
- bugzilla.redhat.com/show_bug.cgi?id=2440895
- nvd.nist.gov/vuln/detail/CVE-2026-2733
- github.com/keycloak/keycloak/issues/46462
- github.com/keycloak/keycloak/commit/743ac24081b2c6da36aac3775147ec5b80c2861e
- github.com/advisories/GHSA-fjf4-6f34-w64q
- access.redhat.com/errata/RHSA-2026:3947
- access.redhat.com/errata/RHSA-2026:3948
- nvd.nist.gov/vuln/detail/CVE-2026-2733
- cve.org/CVERecord?id=CVE-2026-2733
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.