Skip to content

GHSA-q79r-r9xg-r863 CVE-2026-55425

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

Medium Maven
Severity
5.0 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.41%
Chance of exploitation in the next 30 days. Higher than 35.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-213 Exposure of Sensitive Information Due to Incompatible Policies
Fix
7.1.4
Upgrade org.graylog2:graylog2-server to this version or later

Description

Impact

A vulnerability was found in Graylog's API endpoint for retrieving system catalog entity titles. Authenticated users could retrieve database fields of supported entities by sending a custom API request. These fields can include e.g. the password hash of a user (but not the password itself), which should not be returned through the API, regardless of the endpoint. Permission checks do still apply, so users can retrieve their own password hash, but not those of other users. The admin user (or any user with an admin role) can retrieve password hashes of all users.

Patches

This issue has been patched in Graylog 7.1.4. In this version, an allow list will be used to check if protected fields are being accessed, refusing those requests. Affected users should upgrade to 7.1.4 or above to remediate the vulnerability.

Workarounds

There is no known workaround. Upgrading to a patched version is recommended.

Credits

Thanks to Evelynkaz for reporting.

Affected versions

Maven

PackageVulnerableFixed in
org.graylog2:graylog2-server
>= 7.1.0, < 7.1.4
7.1.4

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.graylog2:graylog2-server Maven → 7.1.4

maven
<dependency><groupId>org.graylog2</groupId><artifactId>graylog2-server</artifactId><version>7.1.4</version></dependency>
gradle
implementation("org.graylog2:graylog2-server:7.1.4")

Severity breakdown

CVSS 3.1 5.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

Weakness

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

The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-m9c2-85gv-8xr5
Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards
Medium Also affects org.graylog2:graylog2-server
GHSA-j769-9gv9-65gr
Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
Medium Also affects org.graylog2:graylog2-server
GHSA-gqr6-r77p-c2pj
Fortigate syslog message parser can be exploited to modify or delete fields from the original message
High Also affects org.graylog2:graylog2-server
GHSA-3m86-c9x3-vwm9
Graylog vulnerable to privilege escalation through API tokens
High Also affects org.graylog2:graylog2-server
GHSA-76vf-mpmx-777j
Graylog Allows Session Takeover via Insufficient HTML Sanitization
Medium Also affects org.graylog2:graylog2-server
GHSA-q9q2-3ppx-mwqf
Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser
High Also affects org.graylog2:graylog2-server
GHSA-q7g5-jq6p-6wvx
Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong value
Medium Also affects org.graylog2:graylog2-server
GHSA-p6gg-5hf4-4rgj
Graylog vulnerable to instantiation of arbitrary classes triggered by API request
High Also affects org.graylog2:graylog2-server
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor