3.8
LOW CVSS 3.1
CVE-2026-2733
Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol
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.

INFO

Published Date :

Feb. 19, 2026, 8:16 a.m.

Last Modified :

Feb. 19, 2026, 3:52 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-2733 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 LOW 53f830b8-0a3f-465b-8143-3b8a9948e749
CVSS 3.1 LOW MITRE-CVE
CVSS 3.1 LOW [email protected]
Solution
Address token issuance after disabling Docker registry client access in Keycloak.
  • Verify Keycloak Docker v2 endpoint.
  • Apply any available patches or updates.
  • Test token issuance for disabled clients.
  • Confirm administrative controls prevent access.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-2733.

URL Resource
https://access.redhat.com/security/cve/CVE-2026-2733
https://bugzilla.redhat.com/show_bug.cgi?id=2440895
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-2733 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-2733 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-2733 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-2733 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Feb. 19, 2026

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
    Added CWE CWE-285
    Added Reference https://access.redhat.com/security/cve/CVE-2026-2733
    Added Reference https://bugzilla.redhat.com/show_bug.cgi?id=2440895
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 3.8
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact