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

Elasticsearch-grok Potential Node Crash due to Large Recursion in `innerForbidCircularReferences` FunctionGHSA-ghfh-p92w-j4mg

MEDIUMFix: elastic/elasticsearch@4e5c680

GHSA-ghfh-p92w-j4mg is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.elasticsearch:elasticsearch-grok. A fix is available for org.elasticsearch:elasticsearch-grok — see the affected versions and patch details below.

Also known asBIT-elasticsearch-2024-52980CVE-2024-52980
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-ghfh-p92w-j4mg.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk
0.00%0.35%0.70%1.06%0.3%0.6%May 26Aug 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

1 pkg affected
☕org.elasticsearch:elasticsearch-grok

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

A flaw was discovered in Elasticsearch, where a large recursion using the innerForbidCircularReferences function of the PatternBank class could cause the Elasticsearch node to crash.

A successful attack requires a malicious user to have read_pipeline Elasticsearch cluster privilege assigned to them.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.elasticsearch:elasticsearch-grok≥ 7.17.0&&< 8.15.18.15.1org.elasticsearch:elasticsearch-grok:8.15.1

Affected Products

1 product · 1 configurations
Application
elasticsearchelastic
≥ 7.17.0 && < 8.15.1
range

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-grok, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.elasticsearch:elasticsearch-grok to 8.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghfh-p92w-j4mg 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

A flaw was discovered in Elasticsearch, where a large recursion using the innerForbidCircularReferences function of the PatternBank class could cause the Elasticsearch node to crash. A successful attack requires a malicious user to have read_pipeline Elasticsearch cluster privilege assigned to them.
O3 Security · Impact-Aware SCA

Is GHSA-ghfh-p92w-j4mg in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Elasticsearch-grok Potential Node Crash due to Large…