Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68390: CWE-770 Allocation of Resources Without Limits or Throttling in Elastic Elasticsearch

0
Medium
VulnerabilityCVE-2025-68390cvecve-2025-68390cwe-770
Published: Thu Dec 18 2025 (12/18/2025, 22:17:41 UTC)
Source: CVE Database V5
Vendor/Project: Elastic
Product: Elasticsearch

Description

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow an authenticated user with snapshot restore privileges to cause Excessive Allocation (CAPEC-130) of memory and a denial of service (DoS) via crafted HTTP request.

AI-Powered Analysis

AILast updated: 12/18/2025, 22:41:38 UTC

Technical Analysis

CVE-2025-68390 is a vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) in Elastic's Elasticsearch product, affecting versions 7.0.0, 8.0.0, 9.0.0, and 9.2.0. The flaw allows an authenticated user who possesses snapshot restore privileges to craft HTTP requests that trigger excessive memory allocation within the Elasticsearch service. This excessive allocation can overwhelm system resources, leading to a denial of service (DoS) condition where the Elasticsearch node becomes unresponsive or crashes. The vulnerability exploits the lack of resource throttling or limits when processing snapshot restore operations, which are typically used for backup and recovery purposes. Since the attack requires authentication with specific privileges, it is not exploitable by anonymous users, and no user interaction is needed beyond sending the malicious request. The CVSS 3.1 base score of 4.9 reflects a medium severity, with the impact confined to availability (no confidentiality or integrity impact). No public exploits or patches are currently available, but the vulnerability is published and should be addressed promptly. This vulnerability could be leveraged by insiders or compromised accounts to disrupt Elasticsearch services, impacting applications and services relying on its search and indexing capabilities.

Potential Impact

For European organizations, the impact of CVE-2025-68390 primarily involves service availability degradation or outages of Elasticsearch clusters. Many enterprises, government agencies, and critical infrastructure providers in Europe rely on Elasticsearch for real-time data indexing, search, and analytics. A successful exploitation could disrupt business operations, delay data processing, and impact dependent applications such as security monitoring, e-commerce platforms, and content delivery. The requirement for authenticated access with snapshot restore privileges limits the attack surface but does not eliminate risk, especially in environments with insufficient privilege management or compromised credentials. In sectors like finance, healthcare, and public administration, such disruptions could have cascading effects on operational continuity and regulatory compliance. Additionally, denial of service incidents can increase operational costs and damage organizational reputation. Given the widespread adoption of Elasticsearch in Europe, the threat is significant but manageable with proper controls.

Mitigation Recommendations

To mitigate CVE-2025-68390, European organizations should implement the following specific measures: 1) Restrict snapshot restore privileges strictly to trusted administrators and service accounts; enforce the principle of least privilege. 2) Monitor and audit all snapshot restore operations and related API calls to detect unusual or excessive resource consumption patterns. 3) Employ network segmentation and access controls to limit which users and systems can communicate with Elasticsearch snapshot restore endpoints. 4) Configure Elasticsearch resource limits and quotas where possible to prevent excessive memory allocation during snapshot operations. 5) Prepare incident response plans for Elasticsearch DoS scenarios, including automated alerts and failover procedures. 6) Stay updated with Elastic’s security advisories and apply patches or updates promptly once released. 7) Consider deploying Web Application Firewalls (WAFs) or API gateways that can detect and block anomalous snapshot restore requests. 8) Use multi-factor authentication (MFA) for accounts with elevated privileges to reduce risk of credential compromise. These targeted actions go beyond generic advice by focusing on privilege management, monitoring, and resource control specific to snapshot restore functionality.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
elastic
Date Reserved
2025-12-16T19:18:49.563Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69447f924eb3efac36af9a62

Added to database: 12/18/2025, 10:26:26 PM

Last enriched: 12/18/2025, 10:41:38 PM

Last updated: 12/19/2025, 6:58:19 AM

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats