CVSS 4.0
2.1 lowCVSS: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:PCVE-2026-122014
Low (2.1).
A vulnerability has been found in NPC-Worldwide npcpy up to 2.1.27. This affects the function load_sft_model of the file npcpy/ft/sft.py. The manipulation of the argument base_model_name_or_path leads to code injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Severity
CVSS 3.1
6.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
CWE-94 Improper Control of Generation of Code (Code Injection) - OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-122014 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-122014?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-122014?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-122014 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| NPC-Worldwide npcpy | 2.1.0 |
| NPC-Worldwide npcpy | 2.1.1 |
| NPC-Worldwide npcpy | 2.1.2 |
| NPC-Worldwide npcpy | 2.1.3 |
| NPC-Worldwide npcpy | 2.1.4 |
| NPC-Worldwide npcpy | 2.1.5 |
| NPC-Worldwide npcpy | 2.1.6 |
| NPC-Worldwide npcpy | 2.1.7 |
| NPC-Worldwide npcpy | 2.1.8 |
| NPC-Worldwide npcpy | 2.1.9 |
| NPC-Worldwide npcpy | 2.1.10 |
| NPC-Worldwide npcpy | 2.1.11 |
| NPC-Worldwide npcpy | 2.1.12 |
| NPC-Worldwide npcpy | 2.1.13 |
| NPC-Worldwide npcpy | 2.1.14 |
| NPC-Worldwide npcpy | 2.1.15 |
| NPC-Worldwide npcpy | 2.1.16 |
| NPC-Worldwide npcpy | 2.1.17 |
| NPC-Worldwide npcpy | 2.1.18 |
| NPC-Worldwide npcpy | 2.1.19 |
| NPC-Worldwide npcpy | 2.1.20 |
| NPC-Worldwide npcpy | 2.1.21 |
| NPC-Worldwide npcpy | 2.1.22 |
| NPC-Worldwide npcpy | 2.1.23 |
| NPC-Worldwide npcpy | 2.1.24 |
| NPC-Worldwide npcpy | 2.1.25 |
| NPC-Worldwide npcpy | 2.1.26 |
| NPC-Worldwide npcpy | 2.1.27 |
Attack patterns (CAPEC)
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
- CAPEC-242 Code Injection Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37).