Skip to content
VulniPulse
Advisory severityCritical9.1Apache Software Foundation

Critical [CVE-2026-40682] Apache OpenNLP: XXE via Dictionary Parsing in DictionaryEntryPersistor

This critical-severity Apache Software Foundation advisory covers CVE-2026-40682 affecting Apache OpenNLP DictionaryEntryPersistor.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-40682 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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

Versions Affected: before 2.5.9, before 3.0.0-M3

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.

Affected versions
  • Apache OpenNLP 2.0 before 2.5.9
  • Apache OpenNLP 3.0.0-M1 before 3.0.0-M3
  • Apache OpenNLP before 1.9.5

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Fixed versions
  • 2.5.9
  • 3.0.0-M3
  • 1.9.5

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation: 2.x users should upgrade to 2.5.9.
  • 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.

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.