CVE-2026-55867

Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens

Published Aug 28, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.

Analysis

AI-generated

Technical impact

The vulnerability in Graylog's token revocation API allows any authenticated user with the USERS_TOKENREMOVE permission to delete tokens owned by other users, including service accounts or administrators. It does not expose the token contents but removes the token, causing integrity loss and potentially disabling token‑based integrations. The flaw is a classic authorization bypass (CWE‑639) where the API checks the requested userId before resolving the token and fails to verify that the token belongs to that user before destroying it.

Affected Systems

Graylog Server versions from 6.2.0 up to but not including 6.3.12, and all 7.x releases prior to 7.0.7 and 7.1.2 remain vulnerable. The bug was fixed in Graylog 6.3.12, 7.0.7, and 7.1.2.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and peak exploit probability (EPSS) is not available. The vulnerability is not listed in CISA’s KEV catalog, suggesting limited public exploit data. The likely attack vector requires an authenticated user who can assign the USERS_TOKENREMOVE permission; the attacker supplies a victim’s userId in the path, causing the target’s tokens to be deleted. Compromise of token holders can disrupt automated workflows and integrations but does not directly expose confidential data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply Graylog updates that include the fix (Graylog 6.3.12, 7.0.7, or 7.1.2).
  • Restrict the USERS_TOKENREMOVE permission to only trusted administrators and audit any assignments to this permission.
  • Configure audit logs to monitor and alert on DELETE /users/{userId}/tokens/{idOrToken} requests by users without ownership of the target account.

Generated by OpenCVE AI on August 28, 2026 at 23:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-j769-9gv9-65gr Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Graylog2
Graylog2 graylog2-server
Vendors & Products Graylog2
Graylog2 graylog2-server
Type Values Removed Values Added
Description Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.
Title Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 31, 2026, 6:38 PM
Reserved
Jun 17, 2026, 4:44 PM
Status
Deferred
Published
Aug 28, 2026, 11:17 PM
Modified
Sep 9, 2026, 9:09 PM