CVE-2026-2733

lowpriority · track · 0EPSS 0.004 · 31 %ileDEEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.37% (31st) EPSS
CVSS 3.8 · low
Is it mine?
5 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · cert_bund · osv

EPSS · scored 2026-10-27

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

3.8
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.13.8lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:Nsecondary · ENISA EU
v3.13.8lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:Nsecondary · secalert@redhat.com USexploitability 1.2 · impact 2.5
v3.13.8lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:Nsecondary · OSV
v3.13.5lowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (5)

Products and version ranges known to be affected.

05

advisories (2)

Vendor and ecosystem advisories describing this.

  • WID-SEC-W-2026-0454Keycloak: Schwachstelle ermöglicht Umgehen von SicherheitsvorkehrungenDeutsch2026-02-18csaf · cert_bundDE

    Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Keycloak ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

  • GHSA-fjf4-6f34-w64qKeycloak: Missing Check on Disabled Client for Docker Registry Protocol2026-02-19ghsa · osvUS

    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.

06

also known as (3)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2026-02-19modified 2026-06-17
08

references (11)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan