Arbitrary Class Instantiation via Model Manifest in Apache OpenNLP ExtensionLoader Versions Affected: before 1.9.5, before 2.5.9, before 3.0.0-M3 Description:  The ExtensionLoader.instantiateExtension(Class, String) method loa…

Overview

Arbitrary Class Instantiation via Model Manifest in Apache OpenNLP ExtensionLoader

Versions Affected: before 1.9.5, before 2.5.9, before 3.0.0-M3

Description: 

The ExtensionLoader.instantiateExtension(Class, String) method loads a class by its fully-qualified name via Class.forName() and invokes its no-arg constructor, with the class name sourced from the manifest.properties entry of a model archive. The existing isAssignableFrom check correctly rejects classes that are not subtypes of the expected extension interface (BaseToolFactory for factory=, ArtifactSerializer for serializer-class-*), but the check runs after Class.forName() has already loaded and initialized the named class.

Class.forName() with default initialization semantics executes the target class's static initializer before returning, so an attacker who can supply a crafted model archive can cause the static initializer of any class on the classpath to run during model loading, regardless of whether that class passes the subsequent type check.

Exploitation requires a class with attacker-useful side effects in its static initializer (for example, JNDI lookup, outbound network I/O, or filesystem access) to be present on the classpath, so this is not a drop-in remote code execution; however, the attack surface grows as third-party model distribution becomes more common (community model repositories, Hugging Face-style sharing), where users routinely load model files from origins they do not control. A secondary, narrower vector affects deployments that ship legitimate BaseToolFactory or ArtifactSerializer subclasses with side-effecting no-arg constructors: a malicious manifest can name such a class and force its constructor to run during model load.

Mitigation: 

• 2.x users should upgrade to 2.5.9.
• 3.x users should upgrade to 3.0.0-M3.

Note: The fix introduces a package-prefix allowlist that is consulted before Class.forName() is invoked, so the static initializer of a disallowed class is never executed. Classes under the opennlp. prefix remain permitted by default. Deployments that load models referencing factories or serializers outside opennlp.* must opt those packages in, either programmatically via ExtensionLoader.registerAllowedPackage(String) before the first model load, or by setting the OPENNLP_EXT_ALLOWED_PACKAGES system property to a comma-separated list of allowed package prefixes.

Users who cannot upgrade immediately should ensure that all model files are sourced from trusted origins and should audit their classpath for classes with side-effecting static initializers or constructors, particularly any that perform JNDI lookups, network requests, or filesystem operations during class initialization.

Affected

• opennlp < 2.5.9
• opennlp = 3.0.0

Remediation

Upgrade past the affected range:

• opennlp 2.5.9

Vendor advisories

• RHSA-2026:65126 · Red Hat · fixed in: Red Hat OpenShift AI 2.25 · released 2026-09-08 · advisory
• Red Hat VEX · Important · affected: Red Hat Fuse 7, Red Hat OpenShift AI (RHOAI) · no fix planned: Red Hat Fuse 7, Red Hat OpenShift AI (RHOAI) · updated 2026-09-08 · vex

Package advisory (CVE-2026-42027)

Affected packages:

• org.apache.opennlp:opennlp-tools >= 3.0.0-M1, < 3.0.0-M3
• org.apache.opennlp:opennlp-tools >= 2.0.0, < 2.5.9
• org.apache.opennlp:opennlp-tools < 1.9.5

Patched in:

• org.apache.opennlp:opennlp-tools 3.0.0-M3
• org.apache.opennlp:opennlp-tools 2.5.9
• org.apache.opennlp:opennlp-tools 1.9.5

Source: https://github.com/advisories/GHSA-cx4m-2p55-rw7j