GHSA-m9c2-85gv-8xr5 CVE-2026-69190

Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards

Medium Maven

Severity: 6.3 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.42%; Chance of exploitation in the next 30 days. Higher than 36.60% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-639 Authorization Bypass Through User-Controlled Key; CWE-862 Missing Authorization
Fix: 6.3.14; Upgrade org.graylog2:graylog2-server to this version or later

Description

Impact

A vulnerability was found in Graylog's API endpoint for updating saved searches and dashboards. A user with edit permissions on a dashboard or saved search could grant owner permissions to an arbitrary account, which could then be used to delete the respective saved search or dashboard or to remove the original owner's access.

Patches

This issue has been patched in the following Graylog versions: 6.3.14, 7.0.9, 7.1.4. Affected users should upgrade to one of these versions or above to remediate the vulnerability.

Graylog Cloud has already been patched.

Workaround

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

Credits

Thanks to Jan Kahmen, turingpoint for reporting.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.graylog2:graylog2-server	`>= 6.3.0, < 6.3.14`	`6.3.14`
org.graylog2:graylog2-server	`>= 7.0.0, < 7.0.9`	`7.0.9`
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 → `6.3.14`

maven

<dependency><groupId>org.graylog2</groupId><artifactId>graylog2-server</artifactId><version>6.3.14</version></dependency>

gradle

implementation("org.graylog2:graylog2-server:6.3.14")

Severity breakdown

CVSS 3.1 6.3

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

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

Weakness

CWE-639: Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How to prevent it

Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How to prevent it

Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-69190

Packages

github.com/Graylog2/graylog2-server

Timeline

Sep 21, 2026 Published
Sep 24, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
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-q79r-r9xg-r863 Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fields	Medium	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