[GHSA-ghfh-p92w-j4mg] Elasticsearch Potential Node Crash due to Large Recursion in innerForbidCircularReferences Function - #9595
Open
levpachmanov wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
levpachmanov/advisory-improvement-9595
September 17, 2026 11:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
The advisory lists
org.elasticsearch:elasticsearch, but that artifact has nevercontained the vulnerable code. The flaw is in the
libs/grokproject (Grok.java,later
PatternBank.java), which theserverproject — published asorg.elasticsearch:elasticsearch— neither contains nor depends on: the published jarhas zero grok entries at every version from 6.2.4 to 8.15.0, and its sources jar has
zero occurrences of
Grok. No upstream source asserts this coordinate either; Elastic'sCVE record names the product
Elasticsearchand NVD encodescpe:2.3:a:elastic:elasticsearch. The code is published asorg.elasticsearch:elasticsearch-grokfrom 8.5.0 onward, and8.15.0carries thepre-fix string
circular reference in patternwhile8.15.1carries the post-fixcircular reference detected. This changes the entry toorg.elasticsearch:elasticsearch-grok,introduced: 0,fixed: 8.15.1—0becausethe flaw (added in 6.2.4 by
5e0678243) predates the package's first release, so everypublished version below 8.15.1 is affected. Note this removes the Maven signal for
7.17.x and 8.0–8.4.x, which is intended: those releases ship the code only inside the
Elasticsearch distribution, with no Maven coordinate to name, and remain covered by the
CVE record and NVD's product CPE.