# Keycloak's admin API allows low privilege users to use administrative functions Advisory record · `GHSA-2cww-fgmg-4jqc` - **Identifiers:** `GHSA-2cww-fgmg-4jqc` · `CVE-2024-3656` - **State:** Confirmed - **Severity:** CVSS 8.1 High - **Critical:** No - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-284](https://cwe.mitre.org/data/definitions/284.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 11 Jun 2024 - **Updated:** 7 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 11 Jun 2024, 20:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.keycloak:keycloak-services` (Maven): affected `<24.0.5`; fixed in `24.0.5` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Keycloak's org.keycloak:keycloak-services package is affected in versions before 24.0.5. A user with low privileges in a realm, such as an ordinary user with no admin role, can use administrative functions in the Keycloak admin API, which the source says could lead to data breaches or system compromise. Upgrade keycloak-services to version 24.0.5 or later. The source gives few details on the exact requests or conditions involved. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.033, the 88th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 11 Jun 2024, 15:32 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/keycloak/keycloak/security/advisories/GHSA-2cww-fgmg-4jqc) - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2cww-fgmg-4jqc) ## Sources - [GitHub Advisory Database: GHSA-2cww-fgmg-4jqc](https://github.com/advisories/GHSA-2cww-fgmg-4jqc) - [OSV: GHSA-2cww-fgmg-4jqc](https://osv.dev/vulnerability/GHSA-2cww-fgmg-4jqc) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .