Skip to content
Fencer Vulns
medium 4.9

CVE-2025-68390 json

Elasticsearch Allocation of Resources Without Limits or Throttling

published 2025-12-18 10 mo ago modified 2026-09-10 1 mo ago also BIT-elasticsearch-2025-68390 , EUVD-2025-204407 , GHSA-gphj-4h6p-37xq

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.elasticsearch.plugin:x-pack-core 8.19.8, 9.1.8, 9.2.2
  • bitnami elasticsearch 8.19.8, 9.1.8, 9.2.2
  • elastic elasticsearch 8.19.8, 9.1.8, 9.2.2
  • elasticsearch elasticsearch 8.19.8, 9.1.8, 9.2.2
  • org.elasticsearch elasticsearch 8.19.8, 9.1.8, 9.2.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-68390 updated cvss 4.9

elasticsearch: Elasticsearch Allocation of Resources Without Limits or Throttling

  • Red Hat Logging Subsystem for Red Hat OpenShift x-pack-core, elasticsearch-core, openshift-logging/kibana6-rhel8, openshift-logging/elasticsearch6-rhel9, openshift-logging/logging-curator5-rhel9, openshift-logging/elasticsearch-proxy-rhel9, +2 more Red Hat Fuse 7 elasticsearch-core Red Hat JBoss Enterprise Application Platform 7 elasticsearch-core Red Hat JBoss Enterprise Application Platform 8 x-pack-core, elasticsearch-core Red Hat JBoss Enterprise Application Platform Expansion Pack x-pack-core, elasticsearch-core
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
10 mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch.plugin:x-pack-core
<8.19.8
>=9.0.0, <9.1.8
>=9.2.0, <9.2.2
8.19.8
9.1.8
9.2.2
bitnami elasticsearch
<8.19.8
>=9.0.0, <9.1.8
>=9.2.0, <9.2.2
8.19.8
9.1.8
9.2.2

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.