# CVE-2026-116275: AllenAI AllenNLP Registrable Configuration Machinery registrable.py Registrable.resolve_class_name code injection


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-xqjc-ffrh-q4x8

## What is CVE-2026-116275?

CVE-2026-116275 is a medium-severity vulnerability in AllenAI AllenNLP, published on 26 Oct 2026. 

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-116275?


## How do I fix CVE-2026-116275?

No fix has been published for CVE-2026-116275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116275 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116275 and fix it if it is affected.

What it is: CVE-2026-116275 is a medium-severity vulnerability in AllenAI AllenNLP, published on 26 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116275 exists.

Affected product: AllenAI AllenNLP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116275/ (Markdown: https://insights.sbomify.com/CVE-2026-116275/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116275
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116275
- OSV: https://osv.dev/vulnerability/CVE-2026-116275

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116275/
Summaries are generated and may contain mistakes; the official description above is the record.