CVE-2026-82617
Awaiting Analysis Awaiting Analysis - Queue

ReDoS in Apache OpenNLP RegexNameFinder

Vulnerability report for CVE-2026-82617, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-11
Generated
2026-09-11
AI Q&A
2026-09-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
apache opennlp From 2.0.0 (inc) to 2.5.11 (inc)
apache opennlp From 3.0.0-M1 (inc) to 3.0.0-M5 (inc)
apache opennlp 2.5.12
apache opennlp 3.0.0-M6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1333 The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves two regex patterns in Apache OpenNLP (EMAIL and URL) that contain ambiguous nested quantifiers. When these patterns are applied to untrusted text, they can cause super-linear backtracking or unbounded matcher recursion. For EMAIL, a long local-part without @ forces quadratic CPU growth. For URL, many query tokens cause stack overflow due to nested repetitions.

Detection Guidance

To detect this vulnerability, check if your Apache OpenNLP version is between 2.0.0-2.5.11 or 3.0.0-M1-3.0.0-M5. Use commands like 'mvn dependency:tree' for Maven projects or inspect the library version in your application's dependencies.

Impact Analysis

An attacker can exploit this to consume excessive CPU (seconds to minutes per request) or crash threads via StackOverflowError. This leads to denial of service for the application. No special setup is needed beyond using the vulnerable built-in finders.

Mitigation Strategies

Upgrade Apache OpenNLP to version 2.5.12 or 3.0.0-M6 immediately. If using Maven, update the dependency in your pom.xml. For other package managers, replace the vulnerable version with the patched release.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82617. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart