Apache OpenNLP Tools denial of service via regex in coordinate name finder
- Exploited
- No known exploitation
- Fix
- Fixed in org.apache.opennlp:opennlp-tools 2.5.13 · org.apache.opennlp:opennlp-runtime 3.0.0
- Who is exposed
- Not reported
Summary
Apache OpenNLP's built-in regular expression name finder for latitude and longitude coordinates uses a pattern that can consume excessive CPU when given crafted text. An attacker who can supply text that an application analyzes with this name finder can cause a denial of service.
Written by a model
Original description
The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. An attacker who can supply text that an application analyzes with this name finder can cause high CPU consumption, leading to denial of service. Users are recommended to upgrade to version 2.5.13 or 3.0.0, which fix the issue.
What to do
Upgrade to a fixed version: org.apache.opennlp:opennlp-tools 2.5.13 · org.apache.opennlp:opennlp-runtime 3.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120404 (Apache OpenNLP: Denial of service via inefficient regular expression in the coordinate name finder), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120404 (entry last updated 2026-11-19):
Affected:
- Maven package org.apache.opennlp:opennlp-tools: from 2.0.0, fixed in 2.5.13
- Maven package org.apache.opennlp:opennlp-runtime: from 3.0.0-M1, fixed in 3.0.0
Fixed versions: 2.5.13, 3.0.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120404 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120404 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/fz6hry1x6yo03qmd5l012t74krk3kr2l
- http://www.openwall.com/lists/oss-security/2026/11/19/6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120404
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120404"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity6.4/10CVSS 6.4
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
Impact
- Widely used2 packages depend on org.apache.opennlp:opennlp-tools. deps.dev
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/fz6hry1x6yo03qmd5l012t74krk3kr2l |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-120404 |
| Record | NVD · CVE-2026-120404 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/19/6 |
Questions about CVE-2026-120404
Is CVE-2026-120404 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-120404?
org.apache.opennlp:opennlp-tools (Maven): from 2.0.0 before 2.5.13. org.apache.opennlp:opennlp-runtime (Maven): from 3.0.0-M1 before 3.0.0.
Source: cve.now feed data
How do I fix CVE-2026-120404?
Upgrade to a fixed version: org.apache.opennlp:opennlp-tools 2.5.13 · org.apache.opennlp:opennlp-runtime 3.0.0.
Source: cve.now feed data
Related
- CVE-2026-42027Apache OpenNLP: Arbitrary Class Instantiation via Model Manifest in ExtensionLoader
- CVE-2017-12620When loading models or dictionaries that contain XML it is possible to perform an XXE attack, since Apache OpenNLP is a library, this only…
- CVE-2026-40682Apache OpenNLP: XXE via Dictionary Parsing in DictionaryEntryPersistor
- CVE-2026-42440Apache OpenNLP: OOM DoS via Unbounded Array Allocation in AbstractModelReader
- CVE-2026-82617Apache OpenNLP, Apache OpenNLP: ReDoS / stack exhaustion in RegexNameFinderFactory built-in EMAIL and URL patterns
- CVE-2026-67211Apache OpenNLP: OOM DoS via Unbounded Array Allocation in SymSpellModelSerializer
No corrections so far. Something wrong on this page? Report an error.