CVE-2025-68384GHSA-QF7C-7R9H-MM92BIT-ELASTICSEARCH-2025-68384
Elasticsearch Allocation of Resources Without Limits or Throttling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.19.9, 9.1.9, 9.2.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Elastic Elasticsearch
From 7.0.0 · through 7.17.29; From 8.0.0 · through 8.19.8; From 9.0.0 · through 9.1.8; From 9.2.0 · through 9.2.2
- org.elasticsearch.plugin:x-pack-securityMaven
fixed in 8.19.9
- org.elasticsearch.plugin:x-pack-securityMaven
From 9.0.0 · fixed in 9.1.9
- org.elasticsearch.plugin:x-pack-securityMaven
From 9.2.0 · fixed in 9.2.3