# Graylog vulnerable to instantiation of arbitrary classes triggered by API request Advisory record · `GHSA-p6gg-5hf4-4rgj` - **Identifiers:** `GHSA-p6gg-5hf4-4rgj` · `CVE-2024-24824` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** Yes: CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 7 Feb 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Feb 2024, 18:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 8.8 (7.0 or more) and EPSS 0.35 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `org.graylog2:graylog2-server` (Maven): affected `>=2.0.0, <5.1.11 || >=5.2.0-alpha.1, <5.2.4`; fixed in `5.1.11`, `5.2.4` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Graylog (org.graylog2:graylog2-server) versions from 2.0.0 before 5.1.11, and 5.2.0-alpha.1 before 5.2.4, are affected. An attacker with an account holding the clusterconfigentry:create and clusterconfigentry:edit permissions, which are usually granted only to Admin users, can send a crafted HTTP PUT request to the cluster config API to load and instantiate arbitrary classes, potentially running code or exposing file contents. Upgrade to version 5.1.11 or 5.2.4. 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.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.35, the 98th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:18 UTC: First seen by agentprime - 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p6gg-5hf4-4rgj) ## Sources - [GitHub Advisory Database: GHSA-p6gg-5hf4-4rgj](https://github.com/advisories/GHSA-p6gg-5hf4-4rgj) - [OSV: GHSA-p6gg-5hf4-4rgj](https://osv.dev/vulnerability/GHSA-p6gg-5hf4-4rgj) - - - - - - 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: .