NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Elasticsearch vulnerable to Uncontrolled Resource ConsumptionGHSA-2cqf-6xv9-f22w

HIGH

GHSA-2cqf-6xv9-f22w is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.elasticsearch:elasticsearch. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.elasticsearch:elasticsearch — see the affected versions and patch details below.

Also known asBIT-elasticsearch-2023-31418CVE-2023-31418
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.33%1.07%1.81%2.55%0.8%2.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.elasticsearch:elasticsearch☕org.elasticsearch:elasticsearch

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.elasticsearch:elasticsearchall versions7.17.13org.elasticsearch:elasticsearch:7.17.13
☕Mavenorg.elasticsearch:elasticsearch≥ 8.0.0&&< 8.9.08.9.0org.elasticsearch:elasticsearch:8.9.0

Affected Products

2 products · 4 configurations
Application
elastic cloud enterpriseelastic
≤ 2.13.3
1 version
3.6.0
Application
elasticsearchelastic
≥ 8.0.0 && ≤ 8.8.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue has been identified with how Elasticsearch handled incoming req…

nvd.nist.govNVDOct 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.elasticsearch:elasticsearch to 7.17.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cqf-6xv9-f22w is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.
O3 Security · Impact-Aware SCA

Is GHSA-2cqf-6xv9-f22w in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Elasticsearch vulnerable to Uncontrolled Resource…