Is CVE-2026-94399 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-94399 being exploited in the wild.

How severe is CVE-2026-94399?

Medium severity, with a CVSS score of 6.5, published 26 September 2026.

Which products and versions are affected?

Elasticsearch 8.19.22, 9.4.7, 9.5.4 and later (patched).

Is there a fix for CVE-2026-94399?

A patch was published on 2026-09-25: Fixed in versions 8.19.22, 9.4.7, 9.5.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-94399 attacked?

It is attacked over the network.

Am I affected by CVE-2026-94399?

Check whether you run Elasticsearch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-94399: Elasticsearch uncontrolled resource consumption denial of service

CVE-2026-94399 · Severity: medium · CVSS 6.5 · Published 2026-09-26

Elasticsearch, a search and analytics engine used by enterprises to index and query large data volumes, contains a vulnerability that allows authenticated attackers to trigger excessive resource allocation. An attacker with valid credentials can craft requests that consume significant system resources, causing the service to become unresponsive or crash, disrupting business operations that depend on search and analytics availability.

Technologies: Elasticsearch. Vendors: Elastic.

Quick answers

Is CVE-2026-94399 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-94399 being exploited in the wild.
How severe is CVE-2026-94399?: Medium severity, with a CVSS score of 6.5, published 26 September 2026.
Which products and versions are affected?: Elasticsearch 8.19.22, 9.4.7, 9.5.4 and later (patched).
Is there a fix for CVE-2026-94399?: A patch was published on 2026-09-25: Fixed in versions 8.19.22, 9.4.7, 9.5.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94399 attacked?: It is attacked over the network.
Am I affected by CVE-2026-94399?: Check whether you run Elasticsearch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An uncontrolled resource consumption vulnerability (CWE-400) in Elasticsearch permits authenticated users to trigger denial of service via excessive memory or CPU allocation without authorization checks. The vulnerability requires authenticated access (PR:L) and network connectivity, affecting the availability of the search service. Patches are available in versions 8.19.22, 9.4.7, and 9.5.4.

Affected products

Elastic Elasticsearch 8.0.0 to 8.19.21; 9.0.0 to 9.4.6; 9.5.0 to 9.5.3
Elastic Elasticsearch 8.19.22, 9.4.7, 9.5.4 and later (patched)

Timeline

2026-09-26: disclosed: Published on NVD
2026-09-25: patched: Fixed in versions 8.19.22, 9.4.7, 9.5.4

References

https://discuss.elastic.co/t/elasticsearch-8-19-22-9-4-7-9-5-4-security-update-esa-2026-180/390684

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.