# CVE-2026-122015: NPC-Worldwide npcpy MLX Provider response.py get_mlx_response input validation


- **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:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-7hq8-9q58-v935

## What is CVE-2026-122015?

CVE-2026-122015 is a medium-severity vulnerability in NPC-Worldwide npcpy, published on 4 Nov 2026. 

### Official description

A vulnerability was found in NPC-Worldwide npcpy up to 2.1.27. This vulnerability affects the function get_mlx_response of the file npcpy/gen/response.py of the component MLX Provider. The manipulation of the argument model results in improper input validation. The attack can be launched remotely. The exploit has been made public and could be used.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-122015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122015 is a medium-severity vulnerability in NPC-Worldwide npcpy, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122015 exists.

Affected product: NPC-Worldwide npcpy. 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-122015/ (Markdown: https://insights.sbomify.com/CVE-2026-122015/index.md)
```

## Sources

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

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