# Moderate severity vulnerability that affects org.keycloak:keycloak-core

Advisory record · `GHSA-778x-2mqv-w6xw`

- **Identifiers:** `GHSA-778x-2mqv-w6xw` · `CVE-2016-8629`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 18 Oct 2018
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Oct 2018, 16:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.keycloak:keycloak-core` (Maven): affected `<2.4.0`; fixed in `2.4.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Keycloak core (org.keycloak:keycloak-core) versions before 2.4.0 are affected. An attacker holding service account credentials can exploit a missing permission check on user deletion requests to delete users in a separate realm. Upgrade to version 2.4.0 or later.

Written 8 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.019, the 80th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-778x-2mqv-w6xw)

## Sources

- [GitHub Advisory Database: GHSA-778x-2mqv-w6xw](https://github.com/advisories/GHSA-778x-2mqv-w6xw)
- [OSV: GHSA-778x-2mqv-w6xw](https://osv.dev/vulnerability/GHSA-778x-2mqv-w6xw)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-8629>
- <https://access.redhat.com/errata/RHSA-2017:0872>
- <https://access.redhat.com/errata/RHSA-2017:0873>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1388988>
- <https://github.com/advisories/GHSA-778x-2mqv-w6xw>
- <http://rhn.redhat.com/errata/RHSA-2017-0876.html>
- <http://www.securityfocus.com/bid/97392>
- <http://www.securitytracker.com/id/1038180>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-778x-2mqv-w6xw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-778x-2mqv-w6xw/>. Everything for agents: <https://agentprime.io/llms.txt>.
