Path Traversal in elk (CVE-2026-33462)
Summary
Path traversal in elk (CVE-2026-33462). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.19.16, 9.3.5 or later.
Original description
The description as published by the source.
A path traversal vulnerability was identified in Kibana's dashboard management functionality. An authenticated user with limited permissions could create a dashboard with a specially crafted identifier. When an administrator subsequently attempts to delete this dashboard through the Kibana interface, the deletion request is redirected to an unintended internal endpoint, potentially resulting in the unauthorized deletion of user accounts or other resources. Exploitation requires an administrator to perform a delete action on the maliciously crafted dashboard object.
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-33462 has been found in elk.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: upgrade elk to 8.19.16, 9.3.5 or later.
If unsure, ask your IT team or search "elk CVE-2026-33462" on the vendor's site.
CVE-2026-33462 (elk) — CWE-22 / CVSS v3 4.6
Attack vector: remote (network-reachable)
Patched: 8.19.16, 9.3.5 — 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.
Path traversal (CWE-22) exists in elk.
Check the vendor advisory for the affected versions of elk.
Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.
Update to 8.19.16, 9.3.5.
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 8.19.16, 9.3.5ステージング環境で 8.19.16, 9.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory discuss.elastic.co
- web nvd.nist.gov
- web github.com