Skip to content
Fencer Intel
low 3.8

CVE-2026-2733 json

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

published 8mo ago modified last mo. also GHSA-fjf4-6f34-w64q , EUVD-2026-7669

cvss
3.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat build of Keycloak 26.4 26.4-12, 26.4.10-1

Is CVE-2026-2733 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-2733 updated cvss 3.8

org.keycloak/keycloak-services: Keycloak: Missing Check on Disabled Client for Docker Registry Protocol

  • Red Hat Build of Keycloak rhbk/keycloak-rhel9-operator, rhbk/keycloak-operator-bundle Red Hat JBoss Enterprise Application Platform 8 keycloak-services Red Hat JBoss Enterprise Application Platform Expansion Pack keycloak-services Red Hat Single Sign-On 7 keycloak-services
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-12, rhbk/keycloak-rhel9-operator 26.4-12, rhbk/keycloak-operator-bundle 26.4.10-1
    fixed: vendor fix RHSA-2026:3948
  • Red Hat build of Keycloak 26.4.10
    fixed: vendor fix RHSA-2026:3947

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 3.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<=26.5.3
 no fix listed

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.10
  • Red Hat Red Hat Build of Keycloak
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.