CVE-2026-115715
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to denial of service via a specially crafted input value that is processed by an affected phonetic encoder of the analysis-phonetic plugin. An authenticated user with permission to write documents to or run searches against an index that uses an affected encoder can cause an Elasticsearch node to exhaust its heap memory. The node can become unresponsive or terminate.
- Score
- 6.5 medium
- Published
- 2026-11-03
- Links
- NVD · cve.org · Report wrong data
Matched ports (3)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| textproc/py-elasticsearch | py312-elasticsearch | 9.5.1 | unaddressed | sunpoet@FreeBSD.org |
| textproc/elasticsearch8 | elasticsearch8 | 8.19.24 | fixed by update | elastic@FreeBSD.org |
| textproc/elasticsearch94 | elasticsearch94 | 9.4.9 | fixed by update | elastic@FreeBSD.org |
Template for a VuXML entry
Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.
Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>py312-elasticsearch -- FIXME</topic>
<affects>
<package>
<name>py312-elasticsearch</name>
<range><ge>9.5.0</ge><le>9.5.5</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CVE-2026-115715: Allocation of Resources Without Limits or Throttling
(CWE-770) in Elasticsearch can lead to denial of service via a
specially crafted input value that is processed by an affected
phonetic encoder of the analysis-phonetic plugin. An authenticated
user with permission to write documents to or run searches against
an index that uses an affected encoder can cause an Elasticsearch
node to exhaust its heap memory. The node can become unresponsive
or terminate.</p>
</body>
</description>
<references>
<cvename>CVE-2026-115715</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-115715</url>
</references>
<dates>
<discovery>2026-11-03</discovery>
<entry>2026-11-10</entry>
</dates>
</vuln>