Answer in brief
CVE-2026-55867 records a Medium severity vulnerability in Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens. The current sources do not mark it as known exploited. The current feed maps Graylog2/graylog2-server (generic), org.graylog2:graylog2-server (maven), org.graylog2:graylog2-server (maven), org.graylog2:graylog2-server (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Graylog2/graylog2-server (generic), org.graylog2:graylog2-server (maven), org.graylog2:graylog2-server (maven), org.graylog2:graylog2-server (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Graylog2/graylog2-servergeneric | >= 6.2.0, < 6.3.12 || >= 7.0.0-alpha.1, < 7.0.7 || >= 7.1.0-alpha.1, < 7.1.2 | Not reported |
| org.graylog2:graylog2-servermaven | >=6.2.0,<6.3.12 | 6.3.12 |
| org.graylog2:graylog2-servermaven | >=7.0.0,<7.0.7 | 7.0.7 |
| org.graylog2:graylog2-servermaven | >=7.1.0,<7.1.2 | 7.1.2 |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.