# CVE-2026-55425: Graylog: System Catalog titles endpoint can be used to retrieve values of protected database fields

> Authenticated users can retrieve protected database fields, including password hashes, via the System Catalog titles endpoint.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-q79r-r9xg-r863

## What is CVE-2026-55425?

CVE-2026-55425 is a medium-severity vulnerability in graylog2-server, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Graylog is a free and open log management platform. From 7.1.0 until 7.1.4 and 7.2.0-alpha.2, the System Catalog entity titles endpoint in graylog2-server/src/main/java/org/graylog2/rest/resources/system/contentpacks/titles/EntityTitleServiceImpl.java allows an authenticated user to request composite display fields without verifying that every selected field is readable. A user can retrieve protected values, including the password hash on a readable user record; ordinary users are limited to their own permitted records, while administrators can retrieve hashes for all users. This issue is fixed in versions 7.1.4 and 7.2.0-alpha.2.

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

## Which versions are affected by CVE-2026-55425?

2 open source packages ship an affected version, including org.graylog2:graylog2-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.graylog2:graylog2-server` | Maven | From 7.1.0 | 7.1.4 |
| `org.graylog2:graylog2-server` | Maven | From 7.1.0 | 7.1.4 |

## How do I fix CVE-2026-55425?

Upgrade org.graylog2:graylog2-server to 7.1.4 or later.

## Is CVE-2026-55425 being exploited?

There is no known exploitation of CVE-2026-55425 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55425 and fix it if it is affected.

What it is: CVE-2026-55425 is a medium-severity vulnerability in graylog2-server, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55425 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4
- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55425/ (Markdown: https://insights.sbomify.com/CVE-2026-55425/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55425
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55425
- OSV: https://osv.dev/vulnerability/CVE-2026-55425

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55425/
Summaries are generated and may contain mistakes; the official description above is the record.