CVE-2025-68384: Elasticsearch has Excessive Allocation of Resources via Submission of Oversized User Settings Data
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
- discuss.elastic.co/t/elasticsearch-8-19-9-9-1-9-and-9-2-3-security-update-esa-2025-33/384181
- github.com/advisories/GHSA-qf7c-7r9h-mm92
- github.com/elastic/elasticsearch
- github.com/elastic/elasticsearch/commit/ab1d99ae033f2a23a8856b47a2d86652ad63a39a
- github.com/elastic/elasticsearch/commit/b46a4f64baea79c4d3afd58bda39d258de97210a
- github.com/elastic/elasticsearch/pull/138691
- nvd.nist.gov/vuln/detail/CVE-2025-68384
Code Behaviors & Features
Detect and mitigate CVE-2025-68384 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →