Home

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.

PUBLISHED Reserved 2026-02-19 | Published 2026-02-19 | Updated 2026-02-23 | Assigner redhat




LOW: 3.8CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Problem types

Improper Authorization

Product status

Default status
affected

Default status
affected

Default status
affected

Default status
affected

Default status
affected

Default status
affected

Timeline

2026-02-19:Reported to Red Hat.
2026-02-19:Made public.

Credits

Red Hat would like to thank Joy Gilbert and Reynaldo Immanuel for reporting this issue.

References

access.redhat.com/security/cve/CVE-2026-2733 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2440895 (RHBZ#2440895) issue-tracking

cve.org (CVE-2026-2733)

nvd.nist.gov (CVE-2026-2733)

Download JSON