Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-92972 high CVSS 8.6

Vulnerability in SGLang (CVE-2026-92972)

Summary

Vulnerability in SGLang (CVE-2026-92972). Risk of unauthorized operations or information disclosure. Exploitable via PUT /route.

Original description

The description as published by the source.

SGLang through 0.5.19 in prefill/decode disaggregation mode contains an unauthenticated PUT /route endpoint on the prefill bootstrap service that allows attackers to poison the KV transfer routing table. Attackers can supply arbitrary rank_ip and rank_port values to redirect decode workers to attacker-controlled endpoints, causing denial of service or disclosure of KV transfer metadata including session identifiers and tensor-parallel topology parameters.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-92972 has been found in SGLang.
Attackers can target a specific entry point like PUT /route over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SGLang CVE-2026-92972" on the vendor's site.

CVE-2026-92972 (SGLang) — CWE-306 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PUT /route
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in SGLang. Attackers reach the vulnerable code path via PUT /route without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of SGLang. Attack surface: PUT /route.

🔥 Severity

Severity: High (CVSS 8.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PUT /route requests with malformed payloads or SQL meta-characters. Run grep -r 'SGLang' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'SGLang' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で SGLang を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PUT /route' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PUT /route への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against PUT /route on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details