Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55867

Vulnerability in org.graylog2:graylog2-server (CVE-2026-55867)

Summary

Vulnerability in org.graylog2:graylog2-server (CVE-2026-55867). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.1.2 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55867 has been found in org.graylog2:graylog2-server.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.graylog2:graylog2-server to 7.1.2 or later.
If unsure, ask your IT team or search "org.graylog2:graylog2-server CVE-2026-55867" on the vendor's site.

CVE-2026-55867 (org.graylog2:graylog2-server) — CWE-639
Patched: 7.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in org.graylog2:graylog2-server.

📍 Affected scope

Check the vendor advisory for the affected versions of org.graylog2:graylog2-server.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.graylog2:graylog2-server を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.graylog2:graylog2-server to 7.1.2

    ステージング環境で 7.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.graylog2:graylog2-server
[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.0"},{"fixed":"7.1.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details