# CVE-2026-112083: sgl-project SGLang Weight Exporter weight_exporter.py WeightExporter.send_weights_to_remote_instance denial of service

> Remote attackers can cause denial of service in SGLang by manipulating the group_name argument in the weight exporter.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-hqw5-mw82-chh2

## What is CVE-2026-112083?

CVE-2026-112083 is a medium-severity denial of service vulnerability in sgl-project SGLang, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in sgl-project SGLang up to 0.5.19. Affected is the function WeightExporter.send_weights_to_remote_instance of the file python/sglang/srt/model_executor/model_runner_components/weight_exporter.py of the component Weight Exporter. Performing a manipulation of the argument group_name results in denial of service. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The pull request to fix this issue awaits acceptance.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-112083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112083 is a medium-severity denial of service vulnerability in sgl-project SGLang, published on 19 Oct 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-112083 exists.

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

## Sources

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

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