Skip to main content
← All vulnerabilities
CVE-2026-55867GHSA-J769-9GV9-65GR

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.3.12, 7.0.7, 7.1.2
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Graylog2 graylog2-server

    From 6.2.0 · fixed in 6.3.12; From 7.0.0-alpha.1 · fixed in 7.0.7; From 7.1.0-alpha.1 · fixed in 7.1.2

  • org.graylog2:graylog2-serverMaven

    From 6.2.0 · fixed in 6.3.12

  • org.graylog2:graylog2-serverMaven

    From 7.0.0 · fixed in 7.0.7

  • org.graylog2:graylog2-serverMaven

    From 7.1.0 · fixed in 7.1.2

References 9

GitHub · Graylog2/graylog2-server