Vulnerability in elasticsearch (CVE-2026-56149)
Summary
Vulnerability in elasticsearch (CVE-2026-56149). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.19.17, 9.3.6, 9.4.3 or later.
Original description
The description as published by the source.
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted machine learning request that causes excessive memory consumption, which may render the affected node unavailable.
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-56149 has been found in elasticsearch.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade elasticsearch to 8.19.17, 9.3.6, 9.4.3 or later.
If unsure, ask your IT team or search "elasticsearch CVE-2026-56149" on the vendor's site.
CVE-2026-56149 (elasticsearch) — CWE-770 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.19.17, 9.3.6, 9.4.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.
A vulnerability (CWE-770) exists in elasticsearch.
Check the vendor advisory for the affected versions of elasticsearch.
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure.
Update to 8.19.17, 9.3.6, 9.4.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 'elasticsearch' . 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 'elasticsearch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
elasticsearchを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade elasticsearch to 8.19.17, 9.3.6, 9.4.3ステージング環境で 8.19.17, 9.3.6, 9.4.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