Case · DiggingBeagle record

SGLang debug dumper executes caller-controlled Python inside its inference scheduler

With a reused exposed debug route, an ordinary model API key could configure an evaluated filter; a published proof of concept created a marker file inside the model server process.

Scope

SGLang inference servers with the reused-port dumper enabled and insufficient administrative route separation.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
AI role
AGAINST AI
Basis and provenance

A maintainer-facing SGLang issue includes an authenticated ordinary-API-key reproduction of scheduler-process Python code execution when the dumper reused a reachable port. The author observed a marker file, but exposed-deployment prevalence, production compromise and an independently verified fixed release are not established.

Assessed Oct 17, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 14, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-SGLANG-EVAL-ROUTEIssue 44188 shows /dumper/configure sending an HTTP-provided filter expression into Python eval in the model scheduler under the reused-port debug configuration.supported

Basis: reported finding

Link to claim
CLM-SGLANG-MARKER-RCEThe reporter reproduced scheduler-process Python execution using an ordinary configured model API key, evidenced by an on-disk marker.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Disable the exposed dumper in production and require separate enforced administrative authentication where debugging is needed.
  • Replace eval of user-provided expressions with a constrained parser whose object graph cannot reach Python globals.
  • Treat the debug dumper as a separate administrative control plane. Keep it disabled or unreachable to ordinary inference principals in production.
  • Eliminate Python eval for attacker-supplied dumper filters and verify a restricted parser cannot traverse helper-function globals or other objects.

Unknowns and contradictions

  • No verified production compromise or exploitation scale.
  • Patch merge and exact fixed release must be checked against maintained source and changelogs.

Sources and citation

Material revision history

  1. Oct 17, 2026 · Canonical change recorded · new in release · revision 163