CVE-2026-55867

published 28 Aug 2026 · updated 31 Aug 2026

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

5.3MediumCVSS 5.3EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Graylog2>=6.2.0 <6.3.12, >=7.0.0-alpha.1 <7.0.7, >=7.1.0-alpha.1 <7.1.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55867 severity on Zeptric[![CVE-2026-55867](https://zeptric.io/badge/cve/CVE-2026-55867.svg)](https://zeptric.io/cve/CVE-2026-55867)