# CVE-2026-86793: CVE-2026-86793

> Unauthenticated pickle deserialization in SGLang allows remote code execution when authentication keys are not configured.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-m675-99qc-9233

## What is CVE-2026-86793?

CVE-2026-86793 is a critical unsafe deserialization vulnerability in SGLang, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang allows unauthenticated pickle deserialization through /update_weights_from_tensor when no auth keys are configured, and the SafeUnpickler policy can be bypassed because builtins.import and builtins.getattr are resolvable, enabling code execution via pickle REDUCE.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

Apply the vendor's patch.

## Is CVE-2026-86793 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86793 is a critical unsafe deserialization vulnerability in SGLang, published on 11 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-86793 exists.

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

## Sources

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

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