CVE-2026-105245
Deferred Deferred - Pending Action

Cleartext API Key Transmission in SGLang HTTP Endpoint

Publication date: 2026-10-05

Last updated on: 2026-10-05

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-05
Last Modified
2026-10-05
Generated
2026-10-05
AI Q&A
2026-10-05
EPSS Evaluated
N/A
NVD
CVE-2026-105245
EUVD
EUVD-2026-92264

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sgl-project sglang to 0.5.21 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-319 The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
CWE-310 Cryptographic Issues

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-105245 is a vulnerability in SGLang up to version 0.5.21 where the HTTP endpoint /server_info and related endpoints expose sensitive credentials like api_key, admin_api_key, and ssl_keyfile_password in cleartext. This occurs because the ServerArgs dataclass is serialized directly, revealing secrets to unauthorized users, especially when only the admin API key is set.

Detection Guidance

Check if the /server_info or /get_server_info HTTP endpoints are accessible without authentication. Use curl commands like 'curl http://<server-address>/server_info' or 'curl http://<server-address>/get_server_info' to see if sensitive data like api_key or admin_api_key is exposed in the response.

Impact Analysis

An attacker could exploit this to retrieve admin API keys and other secrets, gaining access to privileged endpoints. This allows loading arbitrary model weights, modifying system behavior, or exfiltrating sensitive data like model tensors. The attack is remote and requires low privilege or no authentication in certain configurations.

Compliance Impact

This vulnerability likely violates compliance requirements for protecting sensitive data such as API keys and passwords. GDPR and HIPAA mandate safeguards for personal and health information, and exposing credentials could lead to unauthorized access, data breaches, or loss of confidentiality, resulting in legal and regulatory penalties.

Mitigation Strategies

Apply the patch from the pull request https://github.com/sgl-project/sglang/pull/30343 to redact sensitive fields in API responses. Ensure proper authentication is enforced for all endpoints and avoid exposing the /server_info endpoint publicly.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105245. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart