CVE-2026-5760

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-20. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

SGLang's reranking endpoint (/v1/rerank) achieves Remote Code Execution (RCE) when a model file containing a malcious tokenizer.chat_template is loaded, as the Jinja2 chat templates are rendered using an unsandboxed jinja2.Environment().

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

April 20, 2026

Last Modified

June 3, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_pr, cert.
cert

VU#915947 - SGLang is vulnerable to remote code execution when rendering chat templates from a model file

https://www.kb.cert.org/vuls/id/915947
github_pr

Fix for CVE-2026-5760

Fix merged in sgl-project/sglang PR #23660 on 2026-04-29 — awaiting tagged release

https://github.com/sgl-project/sglang/pull/23660
generic🟡 PoC Available

GitHub - Stuub/SGLang-0.5.9-RCE: Proof of Concept exploitation of CVE-2026-5760 - RCE in SGLang 0.5.9 via malicious GGUF · GitHub

https://github.com/Stuub/SGLang-0.5.9-RCE

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 79× 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.

Showing the most recent 100 of 239 total refreshes for this CVE.

  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 10:34 UTCGHSA enrichment
  17. 2026-08-16 06:24 UTCEG score recompute
  18. 2026-08-16 06:24 UTCGHSA enrichment
  19. 2026-08-15 02:28 UTCEG score recompute
  20. 2026-08-15 02:28 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 22:20 UTCGHSA enrichment
  23. 2026-08-14 18:06 UTCGHSA enrichment
  24. 2026-08-14 12:49 UTCGHSA enrichment
  25. 2026-08-14 08:41 UTCGHSA enrichment
Show 75 more
  1. 2026-08-14 04:33 UTCEG score recompute
  2. 2026-08-14 04:33 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 08:48 UTCGHSA enrichment
  5. 2026-08-13 02:59 UTCGHSA enrichment
  6. 2026-08-12 22:51 UTCGHSA enrichment
  7. 2026-08-12 18:44 UTCEG score recompute
  8. 2026-08-12 18:44 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 01:10 UTCGHSA enrichment
  11. 2026-08-11 21:02 UTCGHSA enrichment
  12. 2026-08-11 16:55 UTCEG score recompute
  13. 2026-08-11 16:54 UTCGHSA enrichment
  14. 2026-08-11 06:37 UTCGHSA enrichment
  15. 2026-08-11 02:30 UTCEG score recompute
  16. 2026-08-11 02:30 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 09:24 UTCGHSA enrichment
  19. 2026-08-10 05:16 UTCGHSA enrichment
  20. 2026-08-10 01:09 UTCGHSA enrichment
  21. 2026-08-09 20:59 UTCGHSA enrichment
  22. 2026-08-09 16:51 UTCEG score recompute
  23. 2026-08-09 16:51 UTCGHSA enrichment
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 12:44 UTCGHSA enrichment
  26. 2026-08-09 07:56 UTCGHSA enrichment
  27. 2026-08-09 03:48 UTCEG score recompute
  28. 2026-08-09 03:48 UTCGHSA enrichment
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 09:50 UTCGHSA enrichment
  31. 2026-08-08 05:42 UTCGHSA enrichment
  32. 2026-08-08 01:34 UTCGHSA enrichment
  33. 2026-08-07 21:26 UTCGHSA enrichment
  34. 2026-08-07 17:18 UTCEG score recompute
  35. 2026-08-07 17:18 UTCGHSA enrichment
  36. 2026-08-07 13:11 UTCGHSA enrichment
  37. 2026-08-06 17:27 UTCEG score recompute
  38. 2026-08-06 17:27 UTCGHSA enrichment
  39. 2026-08-06 13:47 UTCEPSS rescore
  40. 2026-08-06 11:58 UTCGHSA enrichment
  41. 2026-08-06 07:30 UTCGHSA enrichment
  42. 2026-08-06 03:22 UTCGHSA enrichment
  43. 2026-08-05 23:14 UTCEG score recompute
  44. 2026-08-05 23:14 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-04 05:43 UTCGHSA enrichment
  49. 2026-08-04 01:35 UTCGHSA enrichment
  50. 2026-08-03 21:27 UTCEG score recompute
  51. 2026-08-03 21:27 UTCGHSA enrichment
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-03 01:22 UTCGHSA enrichment
  54. 2026-08-02 21:13 UTCGHSA enrichment
  55. 2026-08-02 17:05 UTCGHSA enrichment
  56. 2026-08-02 12:56 UTCEG score recompute
  57. 2026-08-02 12:56 UTCGHSA enrichment
  58. 2026-08-02 02:27 UTCEPSS rescore
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-30 16:28 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-28 15:37 UTCEPSS rescore
  64. 2026-07-27 14:14 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:18 UTCEPSS rescore
  70. 2026-07-24 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:20 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-22 14:08 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCStuub/SGLang-0.5.9-RCE
    First seen Apr 2, 2026

    Proof of Concept exploitation of CVE-2026-5760 - RCE in SGLang 0.5.9 via malicious GGUF

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5760?
CVE-2026-5760 is a critical vulnerability published on April 20, 2026. SGLang's reranking endpoint (/v1/rerank) achieves Remote Code Execution (RCE) when a model file containing a malcious tokenizer.chat_template is loaded, as the Jinja2 chat templates are rendered using an unsandboxed jinja2.Environment().
When was CVE-2026-5760 disclosed?
CVE-2026-5760 was first published in the National Vulnerability Database on April 20, 2026, with the most recent update on June 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5760 actively exploited?
CVE-2026-5760 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.3% of all scored CVEs.
What is the CVSS score of CVE-2026-5760?
CVE-2026-5760 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-5760?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5760, 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-5760

Explore →

Is Your Infrastructure Affected by CVE-2026-5760?

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

Start Free Scan →Browse All CVEs