Skip to content
Fencer Vulns
critical 9.1

CVE-2026-40682 in the critical feed json

Apache OpenNLP: XXE via Dictionary Parsing in DictionaryEntryPersistor

published 2026-05-04 6 mo ago modified 2026-10-26 13 d ago also GHSA-4v8g-86x5-3vrc , EUVD-2026-27003

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

XML External Entity (XXE) via Unsanitized Dictionary Parsing in Apache OpenNLP DictionaryEntryPersistor

Versions Affected: before 2.5.9, before 3.0.0-M3

Description: The DictionaryEntryPersistor class initializes a static SAXParserFactory at class-load time without enabling FEATURE_SECURE_PROCESSING or disabling DTD processing. When create(InputStream, EntryInserter) is invoked, the only feature set on the XMLReader is namespace support — external entity resolution and DOCTYPE declarations remain fully enabled. An attacker who can supply a crafted dictionary file (e.g., a stop-word list or domain dictionary) containing a malicious DOCTYPE declaration can trigger local file disclosure via file:// entity references or server-side request forgery via http:// entity references during SAX parsing, before the application processes a single dictionary entry. This is inconsistent with the project's own XmlUtil.createSaxParser() helper, which correctly sets FEATURE_SECURE_PROCESSING and disallow-doctype-decl and is used by all other XML parsing paths in the codebase. The public Dictionary(InputStream) constructor delegates directly to this method and is the documented API for loading user-supplied dictionaries, making untrusted input a realistic scenario.

Mitigation: 2.x users should upgrade to 2.5.9. 3.x users should upgrade to 3.0.0-M3. Users who cannot upgrade immediately should ensure that all dictionary files are sourced from trusted origins and should consider wrapping the Dictionary(InputStream) constructor with input validation that rejects any XML containing a DOCTYPE declaration before it reaches the parser.

Patch / fix

  • maven org.apache.opennlp:opennlp-tools 1.9.5, 2.5.9, 3.0.0-M3
  • Apache Software Foundation Apache OpenNLP 1.9.5, 2.5.9, 3.0.0-M3
  • apache-opennlp Debian 14 2.5.9-1

debian advisories DEBIAN-CVE-2026-40682

  • opennlp openSUSE Tumbleweed 1.9.5-1.1

opensuse advisories openSUSE-SU-2026:11281-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-40682 updated cvss 7.5

org.apache.opennlp/opennlp-tools: Apache OpenNLP: XML External Entity (XXE) vulnerability via crafted dictionary parsing

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9
    affected: workaround, no fix planned “Will not fix”
  • Red Hat OpenShift AI 2.25 rhoai/odh-trustyai-service-rhel9 1790933094
    fixed: vendor fix RHSA-2026:87410
  • Red Hat OpenShift AI 3.4 rhoai/odh-trustyai-service-rhel9 1791792525
    fixed: vendor fix RHSA-2026:84734
  • Red Hat build of Apache Camel for Spring Boot 4 opennlp-tools Red Hat Data Grid 8 opennlp-tools Red Hat Fuse 7 opennlp-tools, opennlp-maxent Red Hat JBoss Enterprise Application Platform 8 opennlp-tools Red Hat JBoss Enterprise Application Platform Expansion Pack opennlp-tools Red Hat OpenShift AI 2.25 rhoai/odh-rhel9-operator 1792570619, rhoai/odh-vllm-cpu-rhel9 1792018436, rhoai/odh-dashboard-rhel9 1791853525, rhoai/odh-modelmesh-rhel9 1790881700, rhoai/odh-operator-bundle 1792571069, rhoai/odh-vllm-cuda-rhel9 1791358976, +65 more
    +1 more products
    Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1791509689, rhoai/rhai-cli-rhel9 1791509689, rhoai/odh-automl-rhel9 1791535789, rhoai/odh-mlflow-rhel9 1791865967, rhoai/odh-autorag-rhel9 1791557539, rhoai/odh-trainer-rhel9 1791869783, +99 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
6 mo ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.opennlp:opennlp-tools
>=2.0.0, <2.5.9
>=3.0.0-M1, <3.0.0-M3
<1.9.5
2.5.9
3.0.0-M3
1.9.5

Affected products

  • Apache Software Foundation Apache OpenNLP
  • Red Hat Red Hat build of Apache Camel for Spring Boot 4
  • Red Hat Red Hat Data Grid 8
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat OpenShift AI (RHOAI)

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.