Skip to content
Fencer Intel
medium 6.5

CVE-2026-63140 json

Reachable Assertion in Elasticsearch Leading to Denial of Service

published 3mo ago modified 18d ago also BIT-elasticsearch-2026-63140 , EUVD-2026-46433

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

Reachable Assertion (CWE-617) in Elasticsearch can lead to denial of service via Input Data Manipulation (CAPEC-153). A specially crafted search request containing a null value in a specific query clause causes an internal assertion to be raised during query parsing. Because Elasticsearch treats assertion failures as fatal errors, this terminates the affected node process. A low-privileged authenticated user with read access to at least one index can exploit this condition with a single request to cause a node to terminate, disrupting search availability. In a single-node deployment this fully stops Elasticsearch; in a multi-node cluster it reduces cluster capacity for each affected node.

Patch / fix

  • bitnami elasticsearch 8.19.19, 9.3.8, 9.4.4
  • elastic elasticsearch 8.19.19, 9.3.8, 9.4.4
  • elasticsearch elasticsearch 8.19.19, 9.3.8, 9.4.4
  • org.elasticsearch elasticsearch 8.19.19, 9.3.8, 9.4.4

Is CVE-2026-63140 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elasticsearch
>=8.0.0, <8.19.19
>=9.0.0, <9.3.8
>=9.4.0, <9.4.4
8.19.19
9.3.8
9.4.4

Affected products

  • Elastic Elasticsearch

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.