- Veröffentlicht
- 04.05.2026 18:43
- Zuletzt geändert
- 27.10.2026
- EPSS (30 Tage)
- 0.7 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 2 betroffen, 2 behoben, 6 nicht betroffen.
Red Hat Fuse 7
Betroffenwird nicht behoben
opennlp-tools
Red Hat OpenShift AI (RHOAI)
Betroffenwird nicht behoben
rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9
openSUSE Tumbleweed
Behoben
opennlp-1.9.5-1.1, opennlp-morfologik-addon-1.9.5-1.1, opennlp-tools-1.9.5-1.1, opennlp-uima-1.9.5-1.1
Nicht betroffen (6)
Red Hat Data Grid 8Nicht betroffenKomponente nicht enthaltenopennlp-tools
Red Hat JBoss Enterprise Application Platform 8Nicht betroffenverwundbarer Code nicht enthaltenopennlp-tools
Red Hat JBoss Enterprise Application Platform Expansion PackNicht betroffenverwundbarer Code nicht enthaltenopennlp-tools
Red Hat OpenShift AI (RHOAI)Nicht betroffenverwundbarer Code nicht enthaltenrhoai/odh-trustyai-service-rhel8
Red Hat OpenShift AI 2.25Nicht betroffenverwundbarer Code nicht enthaltenrhoai/odh-built-in-detector-rhel9, rhoai/odh-caikit-nlp-rhel9, rhoai/odh-caikit-tgis-serving-rhel9, rhoai/odh-codeflare-operator-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-data-science-pipelines-argo-argoexec-rhel9, rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9, rhoai/odh-data-science-pipelines-operator-controller-rhel9, rhoai/odh-feast-operator-rhel9, rhoai/odh-feature-server-rhel9, rhoai/odh-fms-guardrails-orchestrator-rhel9, rhoai/odh-guardrails-detector-huggingface-runtime-rhel9, rhoai/odh-kf-notebook-controller-rhel9, rhoai/odh-kserve-agent-rhel9, rhoai/odh-kserve-controller-rhel9, rhoai/odh-kserve-router-rhel9, rhoai/odh-kserve-storage-initializer-rhel9, rhoai/odh-kuberay-operator-controller-rhel9, rhoai/odh-kueue-controller-rhel9, rhoai/odh-llama-stack-core-rhel9, rhoai/odh-llama-stack-k8s-operator-rhel9, rhoai/odh-llm-d-inference-scheduler-rhel9, rhoai/odh-llm-d-routing-sidecar-rhel9, rhoai/odh-ml-pipelines-api-server-v2-rhel9, rhoai/odh-ml-pipelines-driver-rhel9 und 51 weitere
Red Hat build of Apache Camel for Spring Boot 4Nicht betroffenverwundbarer Code wird nicht ausgeführtopennlp-tools
Weitere betroffene Pakete (15)
CVEApache Software Foundation/Apache OpenNLP2.0 → 2.5.9, 3.0.0-M1 → 3.0.0-M3, 1.9.5CVE-2026-42027
Debian:12apache-opennlpkein Fix bekanntDEBIAN-CVE-2026-42027
Debian:13apache-opennlpkein Fix bekanntDEBIAN-CVE-2026-42027
Debian:14apache-opennlp2.5.9-1DEBIAN-CVE-2026-42027
Mavenorg.apache.opennlp:opennlp-tools1.9.5GHSA-cx4m-2p55-rw7j
Mavenorg.apache.opennlp:opennlp-tools2.0.0 → 2.5.9GHSA-cx4m-2p55-rw7j
Mavenorg.apache.opennlp:opennlp-tools3.0.0-M1 → 3.0.0-M3GHSA-cx4m-2p55-rw7j
NVDapache:opennlp2.5.9CVE-2026-42027
Ubuntu:20.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
Ubuntu:22.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
Ubuntu:24.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
Ubuntu:25.10apache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
Ubuntu:26.04:LTSapache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
Ubuntu:26.10apache-opennlpkein Fix bekanntUBUNTU-CVE-2026-42027
openSUSE:Tumbleweedopennlp1.9.5-1.1openSUSE-SU-2026:11281-1
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- lists.apache.org/thread/ltlo4powjfc0w2w2yyl1o5tc7q1gcb2y
- www.suse.com/security/cve/CVE-2026-42027
- www.suse.com/support/security/rating/
- bugzilla.suse.com/1263873
- security-tracker.debian.org/tracker/CVE-2026-42027
- nvd.nist.gov/vuln/detail/CVE-2026-42027
- access.redhat.com/errata/RHSA-2026:65126
- access.redhat.com/security/cve/CVE-2026-42027
- bugzilla.redhat.com/show_bug.cgi
- github.com/apache/opennlp
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42027.json
- www.openwall.com/lists/oss-security/2026/05/01/20
- ubuntu.com/security/CVE-2026-42027
- www.cve.org/CVERecord
- www.openwall.com/lists/oss-security/2026/05/01/20
- issues.apache.org/jira/browse/OPENNLP-1820
- github.com/apache/opennlp/pull/1021