CVE-2026-55867 json
Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
published 2026-08-28 2 mo ago modified 2026-09-09 1 mo ago also GHSA-j769-9gv9-65gr , EUVD-2026-68014
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
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.
Patch / fix
- maven org.graylog2:graylog2-server 6.3.12, 7.0.7, 7.1.2
- github.com/Graylog2/graylog2-server@41d3745 commit
- github.com/Graylog2/graylog2-server@4f28013 commit
- github.com/Graylog2/graylog2-server@84b0ffa commit
- github.com/Graylog2/graylog2-server@e5accc5 commit
- github.com/Graylog2/graylog2-server#26049 pull request
- github.com/Graylog2/graylog2-server#26051 pull request
- github.com/Graylog2/graylog2-server#26053 pull request
- github.com/Graylog2/graylog2-server#26055 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | 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 |
| CNA | 4.0 | 5.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| 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 |
Affected products
- Graylog2 graylog2-server
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/Graylog2/graylog2-server/pull/26049
web
-
github.com
/Graylog2/graylog2-server/pull/26051
web
-
github.com
/Graylog2/graylog2-server/pull/26053
web
-
github.com
/Graylog2/graylog2-server/pull/26055
web
-
github.com
/Graylog2/graylog2-server/commit/41d3745d0e52736d06c07d279ca0d72c1616df4c
web
-
github.com
/Graylog2/graylog2-server/commit/4f280138b53dc3bbb5749213e8cb1c8e372f23a2
web
-
github.com
/Graylog2/graylog2-server/commit/84b0ffa0bdf918f6edd2bb23a47254088634b1fc
web
-
github.com
/Graylog2/graylog2-server/commit/e5accc5f4ce48bd61b84bb8e5a13d21f8eac3da5
web
-
github.com
/Graylog2/graylog2-server/security/advisories/GHSA-j769-9gv9-65gr
web
-
github.com
/Graylog2/graylog2-server
package
Sources
- CVE List CVE-2026-55867
- GitHub Advisory GHSA-j769-9gv9-65gr
- NVD CVE-2026-55867
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.