[GHSA-4v8g-86x5-3vrc] Apache OpenNLP DictionaryEntryPersistor Vulnerable to XML External Entity (XXE) via Unsanitized Dictionary Parsing - #8890
Open
maheshwarivijaykumar wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
maheshwarivijaykumar/advisory-improvement-8890
July 30, 2026 13:14
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 affected version range for
org.apache.opennlp:opennlp-toolsincorrectly collapses multiple disjoint CNA-published ranges into a single< 2.5.9range, causing version 1.9.5 to be falsely reported as vulnerable.The Apache Software Foundation (the CNA of record,
security@apache.org) defines three separate affected ranges:[0, 1.9.5)[2.0, 2.5.9)[3.0.0-M1, 3.0.0-M3)with
defaultStatus: unaffected. This represents a fixed → reintroduced → fixed lifecycle: the vulnerability was fixed in 1.9.5, reintroduced in the 2.x branch, and fixed again in 2.5.9. Consequently, 1.9.5 falls within the unaffected gap[1.9.5, 2.0)and should not be flagged as vulnerable.Additionally, the advisory's own resolved-version enumeration is already consistent with this interpretation—it lists 1.9.0–1.9.4 as affected, but does not include 1.9.5. This indicates the version ranges are internally inconsistent with the versions list. Updating the ranges would align them with both the resolved-version enumeration and the CNA record.
Authoritative sources: