Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Check DeepSeek's dsh tool is really running the version with the sandbox-escape fix

Written October 30, 2026

For anyone running DeepSeek's dsh tool — dsh is DeepSeek's harness, the program that runs the agent. Find the copy of the program that actually executes, and read its version: a version number on a download page is not proof of the version your machine runs, and a desktop wrapper can carry its own copy. If the fixed version is not the version that runs, an agent inside its sandbox — the restricted workspace meant to confine it — can switch its own session to danger-full-access, turning off the sandbox and its approval prompts.

The flaw, in brief

CVE-2026-82533, rated CVSS 9.4, covers versions of the tool before 0.1.2-alpha.1. The flaw was in the tool's local control interface: it trusted a client-supplied loopback Host header instead of the real connection origin, so a sandboxed agent — an agent running inside the sandbox, the restricted workspace meant to confine it — could call that interface and set its own session to danger-full-access, which turns off the sandbox and stops approval prompts. The sandbox confined file writes, not reads or network access, so the interface was reachable from inside it. The fix adds one-time-token authentication to the interface. It does not make the sandbox confine reads or network access.

The version number needs care. The fixed code shipped on GitHub as 0.1.2-alpha.1 on 27 August 2026, but that build never reached npm. The first fixed release on npm was 0.1.2-alpha.2, on 30 August 2026. If you install from npm, 0.1.2-alpha.2 is the floor — a machine reporting 0.1.2-alpha.1 from a source build and a machine reporting an older npm release are in different positions, and only the version that actually executes counts.

Steps

  1. Find the binary that executes. Run:
    • command -v dsh — this prints the path of the dsh your shell actually runs.
    • dsh --version — this prints that binary's version.
    Write down both the path and the version. A version printed by a different copy, or read from a release page, is not this answer.
  2. Find the copy inside any desktop wrapper, separately. If you launch the tool from a desktop app or wrapper, that app may bundle its own copy. Look inside the app's install folder for a bundled dsh binary, or read the version the app itself reports, and run the bundled copy's full path with --version. Record its path and version on a separate line. Do not assume the wrapper's copy matches the command-line copy.
  3. Compare each copy against the floor. Any copy below 0.1.2-alpha.2 installed from npm needs an upgrade. A copy at 0.1.2-alpha.1 built from GitHub carries the fix, but it is not an npm release — if you manage installs through npm, move to 0.1.2-alpha.2 or later so future updates follow the normal path.
  4. Upgrade from npm. The official npm package is @deepseek-ai/dsh — that is the package DeepSeek's own README runs from npm (npx @deepseek-ai/dsh web). Run:
    • npm install -g @deepseek-ai/dsh@0.1.2-alpha.2
    Or install a later release. If you normally run the tool through npx rather than a global install, check that copy instead: npx @deepseek-ai/dsh --version. Then repeat step 1 and confirm the version now reports 0.1.2-alpha.2 or later — the path may stay the same, and that is expected. For a bundled wrapper copy, update the wrapper itself through its own update path, then repeat step 2 — upgrading the command-line copy does not upgrade the bundled one.
  5. Repeat the pass after any wrapper or tool update. A wrapper update can replace its bundled copy with an older or newer one. The version that runs is the version you read after the update, not the version the update notes claim.

What can go wrong

Limits

Related playbooks

Sources

Back to: Coding playbooks hub