Live › vulnerability › CVE-2026-116275
Go to dashboardAllenNLP up to 2.10.1 passes a user-supplied type argument into Registrable.resolve_class_name without validation, so the flaw allows code injection. The sources say a public exploit exists and an attacker can trigger it remotely.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 14:30 UTC. All times on this page are UTC.
Teams that run AllenNLP 2.10.1 or earlier in a service that accepts configuration or type names from outside input can be exposed. The flaw sits in the registrable configuration machinery, so an application that only uses AllenNLP with trusted, fixed configs is less exposed. Teams not using AllenNLP can skip it.
No product ranges from the sources yet.
pip show allennlp and compare the version with 2.10.1.allennlp.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability was found in AllenAI AllenNLP up to 2.10.1. This impacts the function Registrable.resolve_class_name of the file allennlp/common/registrable.py of the component Registrable Configuration Machinery. Performing a manipulation of the argument Type results in code injection. The attack may be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.
This page as .md · .json · in your agent: get_signal("CVE-2026-116275")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.