CVE-2026-82617
9.8, criticalThe two built-in name-finder patterns exposed by opennlp.tools.namefind.RegexNameFinderFactory - DEFAULT_REGEX_NAME_FINDER.EMAIL and…
- CVSS
- 9.8, critical critical CVSS v3.1
- EPSS, next 30 days
- 0.8% higher than 54.6% of scored CVEs
- Exploitation
- No public evidence
- Published
- 11 Sept 2026a month ago
Description
The two built-in name-finder patterns exposed by opennlp.tools.namefind.RegexNameFinderFactory - DEFAULT_REGEX_NAME_FINDER.EMAIL and DEFAULT_REGEX_NAME_FINDER.URL - contain ambiguous nested quantifiers. An application that obtains these finders through RegexNameFinderFactory.getDefaultRegexNameFinders(...) and then applies them to untrusted text through RegexNameFinder.find(String[]) or RegexNameFinder.find(String) can be driven into super-linear backtracking or into unbounded matcher recursion by a small crafted input. For the EMAIL pattern, a long run of local-part characters that is never followed by an @ forces the matcher to re-scan to end-of-input from every starting offset. Cost grows quadratically with input length: an input of approximately 32 KB consumes several seconds of CPU in a single find() call and returns no match, and each doubling of the input multiplies the cost roughly four-fold. For the URL pattern, the query-string sub-expression nests a capturing repetition inside an outer repetition. The JDK matcher recurses once per query token, so an input of approximately 4 KB containing many &-separated tokens exhausts the thread stack and causes java.lang.StackOverflowError to propagate out of find(), terminating the calling thread. On a thread created with a smaller stack (for example -Xss512k, typical of server worker pools) approximately 1 KB is sufficient. In both cases an attacker who can supply text for analysis can convert a single request into seconds to minutes of pinned CPU, or into an abrupt thread death, denying service to the embedding application. No authentication, special configuration, or model file is required beyond the application having selected one of the two built-in finders. This issue affects Apache OpenNLP: from 2.0.0 through 2.5.11; from 3.0.0-M1 through 3.0.0-M5. Users are recommended to upgrade to version 2.5.12, or to 3.0.0-M6 for users tracking the 3.0.0 milestone line, which fix the issue.
Details
- Vendor
- Apache Software Foundation
- Product
- Apache OpenNLP
- Weakness
- CWE-1333 (opens in a new tab)
- Status
- Analyzed
- Updated
- 16 Sept 2026
- Assigner
- security@apache.org
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References 2
The kind is read from NVD's tags where present and from the shape of the URL otherwise, so treat it as a hint.
Other Apache Software Foundation CVEs
Every Apache Software Foundation CVE we holdSame vendor in what we hold, not a known link between the flaws.
- CVE-2026-92414 Apache Software Foundation Apache Jackrabbit Session Fixation Vulnerability EPSS 0.7% 9.1, critical
- CVE-2026-104714 Apache Software Foundation Apache Struts Race Condition Vulnerability EPSS 0.7% 8.8, high
- CVE-2026-86089 Apache Software Foundation Apache NiFi Missing Authorization Vulnerability EPSS 0.4% 7.1, high
- CVE-2026-87976 Apache Software Foundation Apache NiFi Registry Path Traversal Vulnerability EPSS 0.8% 8.1, high
- CVE-2026-71257 Apache Software Foundation Apache Wicket Allocation of Resources Without Limits or Throttling Vulnerability EPSS 0.7% 7.5, high
- CVE-2026-74848 Apache Software Foundation Apache APISIX HTTP Request Smuggling Vulnerability EPSS 0.6% 7.5, high
- CVE-2026-75005 Inefficient Algorithmic Complexity vulnerability in Apache APISIX EPSS 0.7% 7.5, high
- CVE-2026-75020 Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache APISIX EPSS 0.5% 8.1, high
Beyond this page
Is CVE-2026-82617 in your network?
This page tells you how dangerous CVE-2026-82617 is out there. Whether it sits on one of your devices, only a scan of your own network can tell. That is what our systems do, every day, for the companies we protect.
-
EXYS7600 OCELOT
Find it before attackers do
Ocelot scans your network on a schedule and reports every vulnerability it finds by its CVE identifier, with its CVSS score and how many of your hosts are affected. A finding like CVE-2026-82617 comes with the devices to patch.
Learn more about EXYS7600 OCELOT -
EXYS7950 KONDRA
Detect it if it's exploited
Until the patch is applied, Kondra monitors your network, events and endpoints in real time. It keeps an inventory of the software installed on every endpoint, and its anomaly detection rules flag what an attacker does once inside.
Learn more about EXYS7950 KONDRA
Assembled from the NVD 2.0 API, the CISA Known Exploited Vulnerabilities Catalog and FIRST EPSS. Scores are as of our last collection on 18 Oct 2026, not the live upstream state.