CVE-2026-15977

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 4, 2026

Advisory Details (1)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

Breaking SGLang's Trust Boundaries | Thoughts | Apoorv Dayal

https://thoughts.apoorvdayal.com/posts/sglang-disclosures/

Vendor Advisories for CVE-2026-15977(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 87× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 03:51 UTCEG score recompute
  2. 2026-08-20 03:51 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 16:43 UTCGHSA enrichment
  5. 2026-08-19 05:31 UTCGHSA enrichment
  6. 2026-08-18 18:27 UTCEG score recompute
  7. 2026-08-18 18:27 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 06:50 UTCGHSA enrichment
  10. 2026-08-17 19:43 UTCEG score recompute
  11. 2026-08-17 19:43 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 07:19 UTCGHSA enrichment
  14. 2026-08-16 20:16 UTCEG score recompute
  15. 2026-08-16 20:16 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 09:13 UTCEG score recompute
  18. 2026-08-16 09:13 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 22:10 UTCGHSA enrichment
  21. 2026-08-15 11:07 UTCEG score recompute
  22. 2026-08-15 11:07 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-15 00:04 UTCGHSA enrichment
  25. 2026-08-14 13:01 UTCGHSA enrichment
Show 62 more
  1. 2026-08-14 01:57 UTCEG score recompute
  2. 2026-08-14 01:57 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 14:54 UTCGHSA enrichment
  5. 2026-08-13 03:51 UTCGHSA enrichment
  6. 2026-08-12 16:48 UTCEG score recompute
  7. 2026-08-12 16:48 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 05:45 UTCGHSA enrichment
  10. 2026-08-11 18:42 UTCEG score recompute
  11. 2026-08-11 18:42 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 07:35 UTCEG score recompute
  14. 2026-08-11 07:35 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 20:32 UTCGHSA enrichment
  17. 2026-08-10 09:27 UTCGHSA enrichment
  18. 2026-08-09 22:24 UTCEG score recompute
  19. 2026-08-09 22:24 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 11:21 UTCGHSA enrichment
  22. 2026-08-09 00:18 UTCEG score recompute
  23. 2026-08-09 00:18 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 13:15 UTCGHSA enrichment
  26. 2026-08-08 02:11 UTCEG score recompute
  27. 2026-08-08 02:11 UTCGHSA enrichment
  28. 2026-08-07 15:08 UTCGHSA enrichment
  29. 2026-08-07 04:05 UTCGHSA enrichment
  30. 2026-08-06 17:02 UTCGHSA enrichment
  31. 2026-08-06 05:58 UTCEG score recompute
  32. 2026-08-06 05:58 UTCGHSA enrichment
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 18:55 UTCGHSA enrichment
  35. 2026-08-05 07:52 UTCGHSA enrichment
  36. 2026-08-04 20:47 UTCEG score recompute
  37. 2026-08-04 20:46 UTCGHSA enrichment
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 12:48 UTCEG score recompute
  40. 2026-08-04 12:48 UTCGHSA enrichment
  41. 2026-08-04 10:38 UTCEPSS rescore
  42. 2026-08-04 01:46 UTCGHSA enrichment
  43. 2026-08-03 14:43 UTCEG score recompute
  44. 2026-08-03 14:43 UTCGHSA enrichment
  45. 2026-08-03 10:35 UTCEPSS rescore
  46. 2026-08-03 03:40 UTCGHSA enrichment
  47. 2026-08-02 16:37 UTCGHSA enrichment
  48. 2026-08-02 05:33 UTCEG score recompute
  49. 2026-08-02 05:33 UTCGHSA enrichment
  50. 2026-08-02 02:26 UTCEPSS rescore
  51. 2026-08-01 18:30 UTCGHSA enrichment
  52. 2026-08-01 07:27 UTCEG score recompute
  53. 2026-08-01 07:27 UTCGHSA enrichment
  54. 2026-08-01 04:15 UTCEPSS rescore
  55. 2026-07-31 20:24 UTCEG score recompute
  56. 2026-07-31 20:24 UTCGHSA enrichment
  57. 2026-07-31 19:48 UTCEG score recompute▲ 7.50
  58. 2026-07-31 19:48 UTCGHSA enrichment
  59. 2026-07-31 19:48 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  60. 2026-07-30 19:29 UTCNVD update
  61. 2026-07-30 18:27 UTCEG score recompute
  62. 2026-07-30 18:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15977?
CVE-2026-15977 is a high vulnerability published on July 30, 2026. 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.
When was CVE-2026-15977 disclosed?
CVE-2026-15977 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15977 actively exploited?
CVE-2026-15977 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-15977?
CVE-2026-15977 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15977?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15977, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15977

Explore →

Is Your Infrastructure Affected by CVE-2026-15977?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs