# CVE-2026-112051: Xinference through 4.0.1 Path Traversal via model_name in Custom Model Registration

> Unauthenticated attackers can write or delete arbitrary JSON files on Windows via path traversal in model registration, potentially leading to code execution.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-xhc4-qrhj-p2jj

## What is CVE-2026-112051?

CVE-2026-112051 is a high-severity path traversal vulnerability in xorbitsai inference, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xinference through 4.0.1 contains a path traversal vulnerability on Windows that allows unauthenticated attackers to write and delete arbitrary .json files via backslash sequences in model_name. Attackers can register a persisted custom model through POST /v1/model_registrations/{model_type} with names like ..\..\evil to overwrite configuration or data files writable by the Xinference process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-112051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112051 is a high-severity path traversal vulnerability in xorbitsai inference, published on 18 Oct 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-112051 in the wild and no public exploit code.

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

## Sources

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

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