PT-2026-90004
CVE-2026-82617
·
Published
2026-09-11
·
Updated
2026-09-17
Description by
CVSS 4.0
10
CriticalMetricsAV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Name of the Vulnerable Software and Affected Versions
Apache OpenNLP versions 2.0.0 through 2.5.11
Apache OpenNLP versions 3.0.0-M1 through 3.0.0-M5
Description
Two built-in name-finder patterns in
opennlp.tools.namefind.RegexNameFinderFactory (specifically DEFAULT REGEX NAME FINDER.EMAIL and DEFAULT REGEX NAME FINDER.URL) contain ambiguous nested quantifiers. When an application uses RegexNameFinderFactory.getDefaultRegexNameFinders(...) and processes untrusted text via RegexNameFinder.find(String[]) or RegexNameFinder.find(String), a crafted input can cause super-linear backtracking or unbounded matcher recursion.For the EMAIL pattern, input lacking an @ symbol can cause quadratic CPU consumption. For the URL pattern, a query-string sub-expression with nested repetitions can exhaust the thread stack, leading to a
java.lang.StackOverflowError. These conditions allow an attacker to cause a denial of service by pinning the CPU or terminating the calling thread. No authentication or special configuration is required if the application uses these finders.Recommendations
Upgrade Apache OpenNLP versions 2.0.0 through 2.5.11 to version 2.5.12.
Upgrade Apache OpenNLP versions 3.0.0-M1 through 3.0.0-M5 to version 3.0.0-M6.
As a temporary workaround, avoid using the
DEFAULT REGEX NAME FINDER.EMAIL and DEFAULT REGEX NAME FINDER.URL patterns when processing untrusted input.Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾