CVE-2026-86793

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-11. 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
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%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 allows unauthenticated pickle deserialization through /update_weights_from_tensor when no auth keys are configured, and the SafeUnpickler policy can be bypassed because builtins.import and builtins.getattr are resolvable, enabling code execution via pickle REDUCE.

CVSS v3
9.8
EG Score
9.8(high)
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
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

CVE-2026-86793: SGLang Bypass Could Let Attackers Run Code on AI Servers | VicOne

https://vicone.com/blog/cve-2026-86793-sglang-bypass-could-let-attackers-run-code-on-ai-servers/
generic

GitHub - sgl-project/sglang: SGLang is a high-performance serving framework for large language models and multimodal models. · GitHub

https://github.com/sgl-project/sglang/tree/main

Vendor Advisories for CVE-2026-86793(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 49× in last 7d / 53× 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-09-20 03:43 UTCGHSA enrichment
  2. 2026-09-19 23:48 UTCGHSA enrichment
  3. 2026-09-19 19:53 UTCGHSA enrichment
  4. 2026-09-19 15:58 UTCEG score recompute
  5. 2026-09-19 15:58 UTCGHSA enrichment
  6. 2026-09-19 11:50 UTCGHSA enrichment
  7. 2026-09-19 07:54 UTCGHSA enrichment
  8. 2026-09-19 03:59 UTCGHSA enrichment
  9. 2026-09-19 00:03 UTCGHSA enrichment
  10. 2026-09-18 20:08 UTCEG score recompute
  11. 2026-09-18 20:08 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 16:12 UTCGHSA enrichment
  14. 2026-09-18 11:38 UTCGHSA enrichment
  15. 2026-09-18 07:43 UTCGHSA enrichment
  16. 2026-09-18 03:48 UTCGHSA enrichment
  17. 2026-09-17 23:53 UTCGHSA enrichment
  18. 2026-09-17 19:43 UTCEG score recompute
  19. 2026-09-17 19:43 UTCGHSA enrichment
  20. 2026-09-17 19:32 UTCEPSS rescore
  21. 2026-09-17 14:35 UTCGHSA enrichment
  22. 2026-09-17 10:38 UTCGHSA enrichment
  23. 2026-09-17 06:43 UTCGHSA enrichment
  24. 2026-09-17 02:46 UTCGHSA enrichment
  25. 2026-09-16 22:49 UTCGHSA enrichment
Show 28 more
  1. 2026-09-16 18:54 UTCGHSA enrichment
  2. 2026-09-16 14:58 UTCEG score recompute
  3. 2026-09-16 14:58 UTCGHSA enrichment
  4. 2026-09-16 14:09 UTCEPSS rescore
  5. 2026-09-16 11:02 UTCGHSA enrichment
  6. 2026-09-16 07:07 UTCEG score recompute
  7. 2026-09-16 07:07 UTCGHSA enrichment
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-16 03:12 UTCGHSA enrichment
  10. 2026-09-15 23:17 UTCGHSA enrichment
  11. 2026-09-15 19:03 UTCGHSA enrichment
  12. 2026-09-15 15:08 UTCGHSA enrichment
  13. 2026-09-15 11:13 UTCGHSA enrichment
  14. 2026-09-15 07:18 UTCGHSA enrichment
  15. 2026-09-15 03:23 UTCEG score recompute
  16. 2026-09-15 03:23 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 23:28 UTCEG score recompute
  20. 2026-09-14 23:28 UTCGHSA enrichment
  21. 2026-09-14 19:22 UTCGHSA enrichment
  22. 2026-09-14 18:55 UTCEG score recompute 9.80
  23. 2026-09-14 18:55 UTCGHSA enrichment
  24. 2026-09-14 18:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  25. 2026-09-11 14:53 UTCGHSA enrichment
  26. 2026-09-11 12:22 UTCNVD update
  27. 2026-09-11 11:45 UTCEG score recompute
  28. 2026-09-11 11:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86793?
CVE-2026-86793 is a critical vulnerability published on September 11, 2026. SGLang allows unauthenticated pickle deserialization through /updateweightsfrom_tensor when no auth keys are configured, and the SafeUnpickler policy can be bypassed because builtins.import and builtins.getattr are resolvable, enabling code execution via pickle REDUCE.
When was CVE-2026-86793 disclosed?
CVE-2026-86793 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86793 actively exploited?
CVE-2026-86793 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 63.3% of all scored CVEs.
What is the CVSS score of CVE-2026-86793?
CVE-2026-86793 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-86793?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86793, 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-86793

Explore →

Is Your Infrastructure Affected by CVE-2026-86793?

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