Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
Impact
Graylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.
The issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.
Patches
The issue has been fixed in the following Graylog versions: 6.3.12, 7.0.7, 7.1.2. Users should upgrade to one of these versions or above to remediate the vulnerability.
Graylog Cloud has already been patched.
Workarounds
There are no feasible workarounds for this issue. Upgrading to a patched version is recommended.
Customers using Graylog Enterprise or Security can review the audit log^1 for suspicious activity. Audit log lines for successful token deletions begin with access token deleted from user.
Credits
Thanks to michaelddickenson and sreelim for reporting.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Java / Kotlin (Maven) | org.graylog2:graylog2-server | >= 6.2.0, < 6.3.12, >= 7.0.0, < 7.0.7, >= 7.1.0, < 7.1.2 | 6.3.12, 7.0.7, 7.1.2 |
Referencias
- https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-j769-9gv9-65gr
- https://github.com/Graylog2/graylog2-server/pull/26049
- https://github.com/Graylog2/graylog2-server/pull/26051
- https://github.com/Graylog2/graylog2-server/pull/26053
- https://github.com/Graylog2/graylog2-server/pull/26055
- https://github.com/Graylog2/graylog2-server/commit/41d3745d0e52736d06c07d279ca0d72c1616df4c
- https://github.com/Graylog2/graylog2-server/commit/4f280138b53dc3bbb5749213e8cb1c8e372f23a2
- https://github.com/Graylog2/graylog2-server/commit/84b0ffa0bdf918f6edd2bb23a47254088634b1fc
- https://github.com/Graylog2/graylog2-server/commit/e5accc5f4ce48bd61b84bb8e5a13d21f8eac3da5
- https://github.com/Graylog2/graylog2-server
- Vector CVSS
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- Debilidad (CWE)
CWE-639- Plataforma
- Java / Kotlin (Maven)
- Paquete
org.graylog2:graylog2-server- Publicada
- 28.08.2026
- Actualizado
- 11.10.2026 13:19
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-j769-9gv9-65gr - CC BY 4.0
Historial de vulnerabilidades: org.graylog2:graylog2-server
Todas las vulnerabilidades publicadas de este paquete (Java / Kotlin (Maven)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 16
- Primera → última
- 05.2022 09.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Alta 5
- Media 8
- Baja 3
Divulgaciones por año
- 2022: 3
- 2023: 3
- 2024: 2
- 2025: 4
- 2026: 4
-
Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.