# CVE-2026-85668: Xinference 3.3.0 Unauthenticated Arbitrary-Path File Read via /v1/models/llm/auto-register

> Unauthenticated attackers can read arbitrary files from the server filesystem via the auto-register endpoint in Xinference.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-xhf8-q5pf-vp28

## What is CVE-2026-85668?

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

### Official description

Xinference (affected commit 4a94832, v3.x) contains an unauthenticated arbitrary-path file read vulnerability in the POST /v1/models/llm/auto-register endpoint, which accepts a caller-supplied model_path parameter without authentication or path confinement. The endpoint reads and parses config.json, tokenizer_config.json, and chat_template.jinja files at the supplied path and reflects the parsed content back to the caller, allowing an unauthenticated attacker to probe the server filesystem and extract content of files with those names in any directory.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-85668 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85668 is a high-severity path traversal vulnerability in xorbitsai inference, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85668 exists.

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-85668/ (Markdown: https://insights.sbomify.com/CVE-2026-85668/index.md)
```

## Sources

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

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