0.0
NA
CVE-2026-15977
CVE-2026-15977
Description

SGLang contains a credential leakage vulnerability in the /server_info endpoint, which will return API keys and SSL keyfile information when only the --admin-api-key is configured.

INFO

Published Date :

July 30, 2026, 7:17 p.m.

Last Modified :

July 30, 2026, 7:17 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-15977 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Restrict access to the /server_info endpoint to prevent API key and SSL keyfile information leakage.
  • Ensure the --admin-api-key is not the only configuration for the endpoint.
  • Review and restrict access to sensitive endpoints.
  • Implement proper access controls for API keys.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-15977.

URL Resource
https://github.com/sgl-project/sglang/security/advisories/GHSA-jx7q-p32r-7wx8
https://thoughts.apoorvdayal.com/posts/sglang-disclosures/
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-15977 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-15977 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-15977 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-15977 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 30, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'SGLang', 'product': 'SGLang', 'versions': [{'status': 'affected', 'version': '0', 'versionType': 'custom', 'lessThanOrEqual': 'v0.5.15'}]}]
    Added Description SGLang contains a credential leakage vulnerability in the /server_info endpoint, which will return API keys and SSL keyfile information when only the --admin-api-key is configured.
    Added Reference https://github.com/sgl-project/sglang/security/advisories/GHSA-jx7q-p32r-7wx8
    Added Reference https://thoughts.apoorvdayal.com/posts/sglang-disclosures/
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.