← Übersicht Nicht im beobachteten Stack

Apache OpenNLP, Apache OpenNLP: ReDoS / stack exhaustion in RegexNameFinderFactory built-in EMAIL and URL patterns

CVE-2026-82617 · DEBIAN-CVE-2026-82617 · UBUNTU-CVE-2026-82617

Kritisch · CVSS 10.0 Ubuntu: mediumRed Hat: Important Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
11.09.2026 19:50
Zuletzt geändert
17.10.2026
EPSS (30 Tage)
0.8 %
CVSS-Vektor
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 2 nicht betroffen.

Nicht betroffen (2)
Red Hat Fuse 7Nicht betroffenverwundbarer Code nicht enthaltenopennlp-maxent, opennlp-tools
Red Hat OpenShift AI (RHOAI)Nicht betroffenverwundbarer Code nicht enthaltenrhoai/odh-trustyai-service-rhel9, rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9
Weitere betroffene Pakete (11)
CVEApache Software Foundation/Apache OpenNLP3.0.0-M1 → 3.0.0-M6CVE-2026-82617
CVEApache Software Foundation/Apache OpenNLP2.0.0 → 2.5.12CVE-2026-82617
Debian:12apache-opennlpkein Fix bekanntDEBIAN-CVE-2026-82617
Debian:13apache-opennlpkein Fix bekanntDEBIAN-CVE-2026-82617
Debian:14apache-opennlp2.5.12-1DEBIAN-CVE-2026-82617
NVDapache:opennlp2.0.0 → 2.5.12CVE-2026-82617
Ubuntu:20.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-82617
Ubuntu:22.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-82617
Ubuntu:24.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-82617
Ubuntu:26.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-82617
Ubuntu:26.10apache-opennlpkein Fix bekanntUBUNTU-CVE-2026-82617

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.