# Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fields

Advisory record · `GHSA-q79r-r9xg-r863`

- **Identifiers:** `GHSA-q79r-r9xg-r863` · `CVE-2026-55425`
- **State:** Confirmed
- **Severity:** CVSS 5.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-213](https://cwe.mitre.org/data/definitions/213.html)
- **Tags:** [CWE-213](https://agentprime.io/advisories/tag/cwe-213.md)
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Aug 2026, 18:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.graylog2:graylog2-server` (Maven): affected `>=7.1.0, <7.1.4`; fixed in `7.1.4`

## Machine-written summary

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

> Graylog Server versions 7.1.0 through 7.1.3 (Maven org.graylog2:graylog2-server) are affected. An authenticated user can send a crafted request to the system catalog titles endpoint and retrieve protected database fields, such as password hashes; users can only see their own hash, while admins can see all users' hashes. Upgrade to Graylog Server 7.1.4 or later. The source lists no workaround.

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

- 5.0 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q79r-r9xg-r863)

## Sources

- [GitHub Advisory Database: GHSA-q79r-r9xg-r863](https://github.com/advisories/GHSA-q79r-r9xg-r863)
- [OSV: GHSA-q79r-r9xg-r863](https://osv.dev/vulnerability/GHSA-q79r-r9xg-r863)
- <https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-q79r-r9xg-r863>
- <https://github.com/Graylog2/graylog2-server/pull/26284>
- <https://github.com/Graylog2/graylog2-server/commit/1d1a91d99c3d2d8993e61c3c52344648163d3a21>
- <https://github.com/Graylog2/graylog2-server/commit/da7767a44233b6a683d0713eed08da31ce0e77b5>
- <https://github.com/Graylog2/graylog2-server>
- <https://github.com/Graylog2/graylog2-server/releases/tag/7.1.4>
- <https://github.com/Graylog2/graylog2-server/releases/tag/7.2.0-alpha.2>

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-q79r-r9xg-r863>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q79r-r9xg-r863/>. Everything for agents: <https://agentprime.io/llms.txt>.