Authenticated service interruption
Published Sep 26, 2026 · Updated Sep 26, 2026
Resource exhaustion in Elastic Elasticsearch 9.2.0 through 9.4.6 and 9.5.0 through 9.5.3 allows remote authenticated users to interrupt service. Elastic identifies excessive allocation but has not disclosed the affected component, attacker-controlled input, or operation that allocates resources without an effective bound. All configurations are affected, but exploitation requires an authenticated user and has no reported confidentiality or integrity impact.
Summary
What happened
Resource exhaustion in Elastic Elasticsearch 9.2.0 through 9.4.6 and 9.5.0 through 9.5.3 allows remote authenticated users to interrupt service. Elastic identifies excessive allocation but has not disclosed the affected component, attacker-controlled input, or operation that allocates resources without an effective bound. All configurations are affected, but exploitation requires an authenticated user and has no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2026-94396
- Published
- Sep 26, 2026
- Updated
- Sep 26, 2026
- Vendor
- Elastic
- Product
- Elasticsearch
- Classifications
- CWE-400, CAPEC-130, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 26, 2026CVE publishedPublication date reported by the CVE source.
- Sep 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.2.0 <=9.4.6
- Affected versionversion=9.5.0 <=9.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started