Elasticsearch privileged authenticated users can cause DoS through Excessive Resource Allocation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2025-68390: 0.38% estimated exploitation activity in the next 30 days; percentile 31.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

19 Dec 2025, 00:31 UTC

Last modified by the source

19 Dec 2025, 21:07 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gphj-4h6p-37xq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68390

Advisory: Elasticsearch privileged authenticated users can cause DoS through Excessive Resource Allocation
IDs: CVE-2025-68390, GHSA-gphj-4h6p-37xq
Record: https://patchnext.com/advisories/cve-2025-68390 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.elasticsearch.plugin:x-pack-core 9.2.2, 9.1.8, 8.19.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.elasticsearch.plugin:x-pack-core: affected < 8.19.8; >= 9.0.0, < 9.1.8; >= 9.2.0, < 9.2.2; fixed in 9.1.8, 8.19.8, 9.2.2

## Suggested inspection (read-only)
- Maven org.elasticsearch.plugin:x-pack-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.elasticsearch.plugin:x-pack-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gphj-4h6p-37xq (GitHub-reviewed advisory GHSA-gphj-4h6p-37xq lists affected ranges: Maven org.elasticsearch.plugin:x-pack-core >=0 =9.0.0 =9.2.0 <9.2.2)

Commands are suggestions: review each one before running it.