Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-69190 medium CVSS 6.3

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

Summary

Vulnerability in org.graylog2:graylog2-server (CVE-2026-69190). 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 updating saved searches and dashboards. A user with edit permissions on a dashboard or saved search could grant owner permissions to an arbitrary account, which could then be used to delete the respective saved search or dashboard or to remove the original owner's access.

Patches

This issue has been patched in the following Graylog versions: 6.3.14, 7.0.9, 7.1.4. Affected users should upgrade to one of these versions or above to remediate the vulnerability.

Graylog Cloud has already been patched.

Workaround

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

Credits

Thanks to Jan Kahmen, turingpoint for reporting.

Source: NIST National Vulnerability Database 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-69190 has been found in org.graylog2:graylog2-server.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/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-69190" on the vendor's site.

CVE-2026-69190 (org.graylog2:graylog2-server) — CWE-639 / CVSS v3 6.3
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-639) 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 6.3/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":"0"},{"fixed":"7.1.4"}]}]

References

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