# CVE-2026-105245: sgl-project sglang HTTP Endpoint http_server.py server_info cleartext transmission

> Remote attackers can intercept API keys transmitted in cleartext via the HTTP endpoint, exposing sensitive credentials.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-fr3j-h92j-cm4p, openSUSE-SU-2026:12118-1

## What is CVE-2026-105245?

CVE-2026-105245 is a medium-severity vulnerability in sgl-project sglang, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in sgl-project sglang up to 0.5.21. This issue affects the function server_info of the file python/sglang/srt/entrypoints/http_server.py of the component HTTP Endpoint. Such manipulation of the argument api_key leads to cleartext transmission of sensitive information. It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-310

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-sglang` | openSUSE:Tumbleweed | All versions | 0.5.21-2.1 |

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

Apply the vendor's patch.

## Is CVE-2026-105245 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105245 is a medium-severity vulnerability in sgl-project sglang, published on 5 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-105245 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-105245/ (Markdown: https://insights.sbomify.com/CVE-2026-105245/index.md)
```

## Sources

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

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