add OpenNLP CVE's Vex files#192
Open
epugh wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
@ppkarwasz would love a review |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds new Solr VEX (Vulnerability Exploitability eXchange) Markdown entries for recently disclosed Apache OpenNLP CVEs that affect Solr versions bundling opennlp-tools-1.9.4.jar via lucene-analysis-opennlp, documenting exploitability conditions and mitigations for Solr deployments.
Changes:
- Add VEX entry for CVE-2026-42440 (OOM DoS via crafted OpenNLP model file).
- Add VEX entry for CVE-2026-42027 (arbitrary class instantiation via OpenNLP model manifest).
- Add VEX entry for CVE-2026-40682 (XXE via OpenNLP dictionary parsing).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| content/solr/vex/2026-05-04-cve-2026-42440.md | New VEX entry describing exploitability conditions and mitigations for OpenNLP OOM model parsing issue. |
| content/solr/vex/2026-05-04-cve-2026-42027.md | New VEX entry describing exploitability conditions and mitigations for OpenNLP class instantiation issue. |
| content/solr/vex/2026-05-04-cve-2026-40682.md | New VEX entry describing exploitability conditions and mitigations for OpenNLP XXE issue. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+23
to
+26
| The vulnerable code is present in the `opennlp-tools-1.9.4.jar` that Solr pulls in transitively via | ||
| `lucene-analysis-opennlp` (Lucene 9.12.3). The 1.9.x line is end-of-life, so there is no patched 1.9 | ||
| release; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which validate the count against an | ||
| upper bound (default 10,000,000, configurable via the `OPENNLP_MAX_ENTRIES` system property) before |
Comment on lines
+26
to
+27
| via `lucene-analysis-opennlp` (Lucene 9.12.3). The 1.9.x line is end-of-life, so there is no | ||
| patched 1.9 release; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which consults a |
Comment on lines
+26
to
+27
| `lucene-analysis-opennlp` (Lucene 9.12.3). The 1.9.x line is end-of-life, so there is no patched 1.9 | ||
| release; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which parse dictionaries with secure |
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
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.
Three fresh CVEs flagged against opennlp-tools 1.9.4, which is bundled in Solr 9.x via lucene-analysis-opennlp:
The fix is opennlp-tools >= 2.5.9. Solr 9.x is currently pinned to 1.9.4 via lucene-analysis-opennlp 9.12.3.
Solr 10.1 (branch_10x) has already been updated to opennlp-tools 2.5.9.
The OpenNLP team is backporting fixes to the 1.x line for these cves and will release a 1.9.5 that we can then include in branch_9x and branch_9_11. https://lists.apache.org/thread/nvzl4g2b6rc149nf54xpnorjso5h0mlp