SSRF (Server-Side Request Forgery) in elk (CVE-2026-49093)
Summary
SSRF in elk (CVE-2026-49093). Confidential information can be exposed externally. Mitigation: upgrade to 9.3.3 or later.
Original description
The description as published by the source.
Server-Side Request Forgery (CWE-918) in Kibana can allow an authenticated user with connector management privileges to bypass the operator-configured connector allowlist, causing the Kibana server to issue outbound requests to destinations the egress controls were intended to block.
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-49093 has been found in elk.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade elk to 9.3.3 or later.
If unsure, ask your IT team or search "elk CVE-2026-49093" on the vendor's site.
CVE-2026-49093 (elk) — CWE-918 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 9.3.3 — 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.
SSRF (CWE-918) exists in elk.
Check the vendor advisory for the affected versions of elk.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 9.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'elk' . 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
-
1Identify exposure identify
grep -r 'elk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
elkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade elk to 9.3.3ステージング環境で 9.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- web discuss.elastic.co
- web github.com