# CVE-2026-31217: Code injection in n/a

> Attackers can execute arbitrary Python code by supplying a malicious module.py file via the --model argument in the optimate project.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-3jxq-4q7m-7pfc

## What is CVE-2026-31217?

CVE-2026-31217 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The _load_model() function in the neural_magic_training.py script of the optimate project in commit a6d302f912b481c94370811af6b11402f51d377f (2024-07-21) allows arbitrary code execution. When a user supplies a directory path via the --model command-line argument, the function reads a module.py file from that directory and executes its contents directly using Python's exec() function. This design does not validate or sanitize the file's content, allowing an attacker who controls the input directory to execute arbitrary Python code in the context of the process running the script.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Nebuly Optimate.

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

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

## Is CVE-2026-31217 being exploited?

There is no known exploitation of CVE-2026-31217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31217 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31217 in the wild and no public exploit code.

Affected product: n/a. 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-31217/ (Markdown: https://insights.sbomify.com/CVE-2026-31217/index.md)
```

## Sources

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

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