Improper Authorization Affecting keycloak-services package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.33% (25th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-KEYCLOAKSERVICES-15516669
  • published13 Mar 2026
  • disclosed19 Feb 2026

Introduced: 19 Feb 2026

CVE-2026-2733  (opens in a new tab)
CWE-285  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 keycloak-services.

NVD Description

Note: Versions mentioned in the description apply only to the upstream keycloak-services package and not the keycloak-services package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1