CVE-2026-2733 | Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol

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: 2026-02-19 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-2733 is rated Low Risk (19.2/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.04%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-2733

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-21 0.06% 0.04% -0.02%
2 2026-02-25 0.05% 0.06% +0.01%
3 2026-02-19 — 0.05% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-2733

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.8 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 2.5 [email protected]

Weakness enumeration for CVE-2026-2733

GitHub Security Advisory for CVE-2026-2733

GHSA-fjf4-6f34-w64q · Severity: low · Ecosystem: maven — Keycloak: Missing Check on Disabled Client for Docker Registry Protocol

OS Trackers for CVE-2026-2733

vendor priority summary link
redhat low — https://access.redhat.com/security/cve/CVE-2026-2733

Affected software / configurations for CVE-2026-2733

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-2733

cvelogic Threat Intelligence