CVE-2025-68390
MEDIUMCVE-2025-68390 is a medium-severity (CVSS 4.9) CWE-770 vulnerability in org.elasticsearch.plugin:x-pack-core. O3 Security confirms whether CVE-2025-68390 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Elasticsearch Allocation of Resources Without Limits or Throttling
Real-World Exposure
org.elasticsearch.plugin:x-pack-core☕org.elasticsearch.plugin:x-pack-core☕org.elasticsearch.plugin:x-pack-coreReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.elasticsearch.plugin:x-pack-core | all versions | 8.19.8 |
| ☕Maven | org.elasticsearch.plugin:x-pack-core | ≥ 9.0.0&&< 9.1.8 | 9.1.8 |
| ☕Maven | org.elasticsearch.plugin:x-pack-core | ≥ 9.2.0&&< 9.2.2 | 9.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch.plugin:x-pack-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.elasticsearch.plugin:x-pack-core to 8.19.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68390 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-68390 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-68390. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-68390 in your dependencies?
O3 detects CVE-2025-68390 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.