Cyber Resilience

CVE-2026-40682

XXE in Apache Opennlp ≤ 2.5.9

XXE
Published
04 May 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0050 40th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2026-40682 is a critical-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Apache Opennlp. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-611

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-43825Same product: Apache Opennlp
CVE-2026-42440Same product: Apache Opennlp
CVE-2026-47898Same vendor: Apache
CVE-2023-48362Same vendor: Apache
CVE-2026-44618Same vendor: Apache
CVE-2025-54988Same vendor: Apache
CVE-2025-68280Same vendor: Apache
CVE-2026-65432Same vendor: Apache
CVE-2023-49733Same vendor: Apache
CVE-2026-49875Same vendor: Apache

Affected Assets

apache
opennlp
3.0.0 · ≤ 2.5.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.1
  • V15.3.2

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Secure configuration settings can disable external entity processing in XML parsers.

SA-11 Developer Testing and Evaluation good match

Developer testing can discover XXE flaws through targeted XML parsing tests.

SI-10 Information Input Validation good match

Input validation can reject or sanitize XML containing external entity references.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Hardened XML parser configurations directly disable external entity resolution.

PR.PS-06 mostly match
prevents

Secure SDLC practices include input validation and safe XML parser configuration that prevent XXE.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover XXE flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Patching eliminates XXE-vulnerable parser versions but is only one aspect of software maintenance.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches XXE via static analysis and dynamic XML fuzzing.

A.8.8 Management of technical vulnerabilities mostly match
finds

Vulnerability management identifies and patches XML libraries with unsafe default entity settings.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and entity handling that directly prevents XXE.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for disabling external entity processing in XML parsers.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include safe parser configuration that mitigates external entity risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards require disabling DTDs and external entities in XML processing.

References