Skip to main content
VulnerabilityPublished

CVE-2025-68384: Elastic Elasticsearch · Unthrottled Resource Allocation

Affects Elastic ElasticsearchSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.elasticsearch/elasticsearchpkg:maven/org.elasticsearch/elasticsearchOther threatsAffected
  • 7.0.0 – 9.2.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict network access to Elasticsearch instances, limiting authenticated user connections to trusted personnel and systems only.
  2. Implement strict resource quotas and limits on user settings data size to prevent oversized submissions.
  3. Monitor Elasticsearch logs and metrics for unusual memory usage patterns or frequent crashes indicative of exploitation attempts.
  4. Employ application-layer firewalls or proxies to filter and validate user settings data before it reaches Elasticsearch.
  5. Segregate Elasticsearch environments to isolate critical workloads from less trusted users.
  6. Stay informed on Elastic's official advisories and apply patches or updates promptly once released.
  7. Conduct regular security assessments and penetration tests focusing on resource exhaustion vectors.
  8. Consider deploying automated restart and alerting mechanisms to minimize downtime in case of crashes.
  9. Educate developers and administrators about safe configuration practices and the risks of resource exhaustion attacks. These measures go beyond generic advice by focusing on proactive resource management, access control, and monitoring tailored to this specific vulnerability.

Description

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) causing a persistent denial of service (OOM crash) via submission of oversized user settings data.

References

Community reviews

Loading reviews…