Vulnerability · CVE-2026-72639
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not acco…
Published Aug 13, 2026 · catalog updated Sep 1, 2026 · the affected product
Last checked Nov 2, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-72639. EPSS is 0.42%. Act only if a listed version of the affected product is installed.
Gaps on this record
- No plain product name is stored. The page cannot tell you which product to check.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-103009 · High
- CVE-2026-103008 · Medium
- CVE-2026-103007 · High
- CVE-2026-103006 · Medium
- CVE-2026-103005 · Medium
- Severity
- Medium6.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.42%
- Remediation
- Version ranges on file
- Affected products
- cpe elastic/elasticsearch
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The allocation occurs before the existing highlighting safety limits are evaluated, so memory exhaustion raises a fatal error that terminates the Elasticsearch node process. This results in a denial of service for the affected node and degrades cluster routing and health. The defect is not volumetric and does not depend on the size of the indexed data, so a single request is sufficient.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe elastic/elasticsearch< 8.19.20
- cpe elastic/elasticsearch< 9.4.5
- cpe elastic/elasticsearch< 9.5.1
How to fix CVE-2026-72639
Upgrade
CVE-2026-72639 lists a fix boundary at 8.19.20. Compare the installed build with that boundary before you change production.
Version check
Affected < 8.19.20
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-72639. EPSS is 0.42%. Act only if a listed version of the affected product is installed.
Which versions are affected?
Compare what you have installed with < 8.19.20, < 9.4.5, < 9.5.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-789. EPSS 0.42%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 13, 2026 · Monitored products — high
Detected
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The
Sep 1, 2026 · Monitored products — high
Updated
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The
Sources
- CVE.orgVulnerability recordCVE-2026-72639
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2026-72639
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 2, 2026
- Monitored products — highNov 1, 2026