cve.bz

CVE-2026-94396 elastic elasticsearch: Uncontrolled Resource Consumption

6.5 mediumEPSS 0.2%

Medium (6.5) in elastic elasticsearch. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-94396 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94396?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94396?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-94396 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elasticsearchfrom 9.2.0 through 9.4.6
Elasticsearchfrom 9.5.0 through 9.5.3

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because an authenticated attacker with network access can trigger excessive memory consumption, causing service unavailability without compromising host confidentiality or integrity. Within Red Hat environments, such as Red Hat OpenShift AI, the component operates in isolated internal service architectures rather than public-facing deployments. Therefore, the risk is contained to localized service disruption caused by authorized users or compromised internal services.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Not affected
Red Hat Quay 3quay/quay-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-94396.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON