Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-55867— Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens

Quick assessment

Affected
Graylog2 graylog2-server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Graylog 是一个免费且开源的日志管理平台。在 6.2.0 至 6.3.12、7.0.7 和 7.1.2 版本中， 端点（由 中的 实现）在解析 所选令牌之前，会先针对攻击者控制的 路径参数检查 权限。一个经过身份验证的用户可以提供一个已授权的 ，而 或 可能解析出属于其他用户（包括服务账户或管理员）的令牌；随后 会删除该令牌，且不会检查 。此问题不会泄露令牌内容，但不授权的删除操作会导致完整性影响，并可能扰乱基于访问令牌的集成。该问题已在 6.3.12、7.0.7 和 7.1.2 版本中修复。

CVSS 5.3 · Medium

Possible ATT&CK Techniques 2 AI

T1079 T1098 · Account Manipulation
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-55867

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Graylog2 graylog2-server >= 6.2.0, < 6.3.12 -

II. Public POCs for CVE-2026-55867

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-55867

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-55867 (8)

Vendor Advisories for CVE-2026-55867 (1)

Same Patch Batch · Graylog2 · 2026-08-28 · 3 CVEs total

CVE-2026-55841 7.5 HIGH Graylog: Fortigate syslog message parser can be exploited to modify or delete fields from
CVE-2026-55425 5.0 MEDIUM Graylog: System Catalog titles endpoint can be used to retrieve values of protected databa

IV. Related Vulnerabilities

Same product: graylog2-server
Same vendor: Graylog2
Same weakness: CWE-639

V. Comments for CVE-2026-55867

No comments yet

Leave a comment