{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2026-2733 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-2733 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-2733 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.3; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-2733/ (Markdown: https://insights.sbomify.com/CVE-2026-2733/index.md)","id":"CVE-2026-2733","markdown":"https://insights.sbomify.com/CVE-2026-2733/index.md","name":"CVE-2026-2733","record":{"aliases":["GHSA-fjf4-6f34-w64q","MINI-39cm-74x6-qjwj","MINI-m9xr-w9pr-qgmc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"Attackers can obtain authentication tokens for disabled Docker registry clients, bypassing administrative controls and gaining unintended access to container resources.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol","id":"CVE-2026-2733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Authorization Bypass in SearchModelVersions in mlflow/mlflow","id":"CVE-2026-2734"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.3"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-fjf4-6f34-w64q"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.3"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-fjf4-6f34-w64q"}],"prev":{"headline":"Missing authorization in Enable Media Replace","id":"CVE-2026-2732"},"products":["Red Hat Build of Keycloak","Red Hat JBoss Enterprise Application Platform 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.10"],"published":"2026-02-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["Red Hat"]},"summary":"Attackers can obtain authentication tokens for disabled Docker registry clients, bypassing administrative controls and gaining unintended access to container resources.","url":"https://insights.sbomify.com/CVE-2026-2733/"}