# CVE-2026-122160: A security vulnerability has been detected in myshell-ai AIlice up to 0.4.0.


- **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:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-6wf7-9xfh-x657

## What is CVE-2026-122160?

CVE-2026-122160 is a medium-severity vulnerability in myshell-ai AIlice, published on 5 Nov 2026. 

### Official description

A security vulnerability has been detected in myshell-ai AIlice up to 0.4.0. This vulnerability affects the function LoadModel_PEFT of the file ailice/core/llm/AModelCausalLM.py of the component HuggingFace Model Wrapper. The manipulation of the argument base_model_name_or_path leads to inclusion of functionality from untrusted control sphere. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-122160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122160 is a medium-severity vulnerability in myshell-ai AIlice, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122160 exists.

Affected product: myshell-ai AIlice. 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-122160/ (Markdown: https://insights.sbomify.com/CVE-2026-122160/index.md)
```

## Sources

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

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