Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-0532 high CVSS 8.6

SSRF (Server-Side Request Forgery) in kibana (CVE-2026-0532)

Summary

SSRF in kibana (CVE-2026-0532). Confidential information can be exposed externally. Mitigation: upgrade to 8.19.10, 9.1.10, 9.2.4 or later.

Original description

The description as published by the source.

External Control of File Name or Path (CWE-73) combined with Server-Side Request Forgery (CWE-918) can allow an attacker to cause arbitrary file disclosure through a specially crafted credentials JSON payload in the Google Gemini connector configuration. This requires an attacker to have authenticated access with privileges sufficient to create or modify connectors (Alerts & Connectors: All). The server processes a configuration without proper validation, allowing for arbitrary network requests and for arbitrary file reads.

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-0532 has been found in kibana.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade kibana to 8.19.10, 9.1.10, 9.2.4 or later.
If unsure, ask your IT team or search "kibana CVE-2026-0532" on the vendor's site.

CVE-2026-0532 (kibana) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.19.10, 9.1.10, 9.2.4 — 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

SSRF (CWE-918) exists in kibana.

📍 Affected scope

Check the vendor advisory for the affected versions of kibana.

🔥 Severity

Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 8.19.10, 9.1.10, 9.2.4.

🛡️ 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. Run grep -r 'kibana' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'kibana' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で kibana を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade kibana to 8.19.10, 9.1.10, 9.2.4

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

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

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

Affected packages

Bitnami kibana
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.19.10"},{"introduced":"9.0.0"},{"fixed":"9.1.10"},{"introduced":"9.2.0"},{"fixed":"9.2.4"}]}]
Bitnami elk
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.19.10"},{"introduced":"9.0.0"},{"fixed":"9.1.10"},{"introduced":"9.2.0"},{"fixed":"9.2.4"}]}]

References

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