MediumGHSA-j769-9gv9-65grCVE-2026-55867

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

Published 28 Aug 2026 · Updated 28 Aug 2026

Is your project on an affected org.graylog2:graylog2-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=6.2.0 <6.3.12
Fixed in
6.3.12
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=6.3.12 -DforceVersion=true
Affected
>=7.0.0 <7.0.7
Fixed in
7.0.7
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=7.0.7 -DforceVersion=true
Affected
>=7.1.0 <7.1.2
Fixed in
7.1.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=7.1.2 -DforceVersion=true

Details

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.

[^1]: https://go2docs.graylog.org/current/interacting_with_your_log_data/audit_log.html

Is GHSA-j769-9gv9-65gr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.graylog2:graylog2-server, and gives you the command that fixes it.

More advisories for org.graylog2:graylog2-server

  • MediumCVE-2026-69190Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards · 22 Sept 2026
  • HighCVE-2026-55841Fortigate syslog message parser can be exploited to modify or delete fields from the original message · 28 Aug 2026
  • MediumCVE-2026-55425Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fields · 28 Aug 2026
  • HighCVE-2025-53106Graylog vulnerable to privilege escalation through API tokens · 30 Jun 2025
  • HighCVE-2025-46827Graylog Allows Session Takeover via Insufficient HTML Sanitization · 7 May 2025
  • HighGHSA-q9q2-3ppx-mwqfGraylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser · 7 May 2025
All 16 advisories for org.graylog2:graylog2-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.