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

> Attackers can obtain authentication tokens for disabled Docker registry clients, bypassing administrative controls and gaining unintended access to container resources.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-fjf4-6f34-w64q, MINI-39cm-74x6-qjwj, MINI-m9xr-w9pr-qgmc

## What is CVE-2026-2733?

CVE-2026-2733 is a low-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-2733?

2 open source packages ship an affected version, including org.keycloak:keycloak-services.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.5.3 | None |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.5.3 | None |

## How do I fix CVE-2026-2733?

Apply the vendor's patch.

## Is CVE-2026-2733 being exploited?

There is no known exploitation of CVE-2026-2733 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2733 and fix it if it is affected.

What it is: CVE-2026-2733 is a low-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2733 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.3; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2733/ (Markdown: https://insights.sbomify.com/CVE-2026-2733/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2733
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2733
- OSV: https://osv.dev/vulnerability/CVE-2026-2733

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2733/
Summaries are generated and may contain mistakes; the official description above is the record.