Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55425 medium CVSS 5.0

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

Summary

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

Original description

The description as published by the source.

Impact

A vulnerability was found in Graylog's API endpoint for retrieving system catalog entity titles. Authenticated users could retrieve database fields of supported entities by sending a custom API request. These fields can include e.g. the password hash of a user (but not the password itself), which should not be returned through the API, regardless of the endpoint. Permission checks do still apply, so users can retrieve their own password hash, but not those of other users. The admin user (or any user with an admin role) can retrieve password hashes of all users.

Patches

This issue has been patched in Graylog 7.1.4. In this version, an allow list will be used to check if protected fields are being accessed, refusing those requests. Affected users should upgrade to 7.1.4 or above to remediate the vulnerability.

Workarounds

There is no known workaround. Upgrading to a patched version is recommended.

Credits

Thanks to Evelynkaz 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-55425 has been found in org.graylog2:graylog2-server.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade org.graylog2:graylog2-server to 7.1.4 or later.
If unsure, ask your IT team or search "org.graylog2:graylog2-server CVE-2026-55425" on the vendor's site.

CVE-2026-55425 (org.graylog2:graylog2-server) — CWE-213 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Patched: 7.1.4 — apply immediately
Workaround: There is no known workaround.
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-213) exists in org.graylog2:graylog2-server.

📍 Affected scope

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

🔥 Severity

Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.1.4.

🛡️ Workaround

Workaround: There is no known workaround.

🔍 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 temporary workaround mitigate 
    There is no known workaround.

    パッチが適用されるまでの応急処置として、There is no known workaround. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.graylog2:graylog2-server to 7.1.4

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

  4. 4
    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.4"}]}]

References

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