Security Alert: Unauthenticated Shutdown in @typespec/spector

Executive answer

A GitHub Security Advisory (GHSA-7q9c-hpx7-9cwm) documents a high-severity (CVSS 7.5) missing-authentication issue in the development/testing package @typespec/spector. The package registers an unauthenticated HTTP route POST /.admin/stop which calls process.exit(0), and the server binds to 0.0.0.0 by default, allowing any network-reachable client to trigger a one-request denial-of-service (DoS). The advisory identifies the vulnerable range as <= 0.1.0-alpha.26 and lists 0.1.0-alpha.27 as the patched version. Source: the GitHub advisory GHSA-7q9c-hpx7-9cwm (published 2026-09-04; advisory metadata used here was generated at 2026-09-06).

This alert is not saying SvelteKit itself is vulnerable. The advisory names @typespec/spector (an npm package in the TypeSpec/microsoft/typespec repository); SvelteKit (sveltejs/kit) is not referenced in the advisory. If you maintain SvelteKit, a SvelteKit-based project, or build systems that may include @typespec/spector in CI or developer tooling, read the dependency and exposure guidance below. For direct evidence and the call chain, see the linked advisory and the reproduced facts that follow GHSA-7q9c-hpx7-9cwm.

Facts from the advisory (what is known)

• Advisory identifier: GHSA-7q9c-hpx7-9cwm. Source: GitHub Security Advisory page: GHSA-7q9c-hpx7-9cwm (published 2026-09-04, advisory metadata used here generated at 2026-09-06).

• Package named in the advisory: @typespec/spector (ecosystem: npm).

• Vulnerability summary in the advisory: @typespec/spector registers a POST /.admin/stop route that performs process.exit(0) without any authentication, Origin check, or IP-source restriction. The server binds to 0.0.0.0 by default, which exposes the route to network-reachable clients. The advisory labels this a Missing Authentication for Critical Function (CWE-306) and assigns a CVSS v3.1 score of 7.5 (High).

• Reproduced call chain in the advisory (paraphrased from the advisory text):

1. CLI command tsp-spector serve <scenariosPaths..> starts the server on the default port (3000) with no host option.
2. Server construction calls start() without a host argument.
3. Router registration mounts the admin routes under / including /.admin/stop.
4. The POST /.admin/stop handler calls process.exit(0) after returning HTTP 202.
5. The server listen() call omits a host, causing Node/Express to bind to 0.0.0.0.

• Proof-of-concept (PoC) and reproduction artifacts are included in the advisory and show that a single unauthenticated POST to /.admin/stop will cause the process to exit and the container or process to stop. The advisory provides example curl and Python PoC usage.

• Affected version range (as reported): <= 0.1.0-alpha.26. Patched in 0.1.0-alpha.27 (advisory metadata).

Is SvelteKit directly affected?

Short answer: No direct evidence in the advisory names SvelteKit (sveltejs/kit) or indicates that SvelteKit packages are vulnerable. The advisory explicitly targets the @typespec/spector package in the TypeSpec repository.

Why we say this:

• The advisory's package field and text reference @typespec/spector and code paths inside the TypeSpec repository; it does not mention SvelteKit or the sveltejs/kit repository. The SvelteKit canonical repository is: https://github.com/sveltejs/kit [source].

Dependency-chain relevance and exposure scenarios

Fact: The advisory identifies a development/testing tool that runs an HTTP server and exposes a shutdown endpoint by default. Development tools and test mock servers are often run locally, in CI, or inside containers.

Architectural inference (explicitly labeled): From the advisory's description and the repository paths it cites, one can infer that @typespec/spector is a mock server used by TypeSpec projects and is started with a CLI command tsp-spector serve. This is an architectural conclusion drawn from the advisory's file paths and CLI references, not from the SvelteKit repository.

Exposure scenarios where this advisory matters to SvelteKit users or other maintainers:

• A developer or automation job running tsp-spector serve on a host or container that is reachable from untrusted networks (shared CI runners, public cloud instances with exposed ports, ephemeral dev containers accessible to other tenants). The advisory explicitly notes the default bind to 0.0.0.0 and lack of host/allowlist options.
• A build or test container image that includes @typespec/spector and runs the server during pipeline steps with ports exposed to other services or workers.

Data image (relevant to dependency/visibility discussion):

How to check if your codebase or CI installs the package (safe verification)

These commands are examples only and are generic, commonly used package-inspection steps. They do not exploit the vulnerability; do NOT send POST requests to the /.admin/stop endpoint as that will trigger the shutdown described in the advisory.

• Check project dependencies locally (npm):

• npm: npm ls @typespec/spector — lists package occurrences in the current node_modules tree.
• pnpm: pnpm why @typespec/spector — explains why the package is present in a pnpm workspace.
• yarn: yarn why @typespec/spector

• Search repository files for references (safe string search):

• git grep "@typespec/spector" or rg "@typespec/spector" in the repo root.

• Check CI images or running containers that may expose ports:

• docker ps --format "{{.Names}} {{.Image}} {{.Ports}}" and inspect images used in pipeline steps.

Affected range and severity

Severity (from advisory): High — CVSS v3.1 base score 7.5 (advisory reported classification: Missing Authentication for Critical Function, CWE-306).

Table: Affected versions and recommended immediate action

Verification commands (examples, safe-by-default)

The advisory includes a PoC that demonstrates the real exploit using an actual POST. We provide only safe, non-mutating checks here.

• Verify package presence in a local project (safe):
• npm: npm ls @typespec/spector (exit code 0 shows presence).
• pnpm: pnpm why @typespec/spector (explains the dependency tree).

• Inspect build/CI images and container ports (safe):
• docker ps --format "{{.Names}} {{.Image}} {{.Ports}}" — look for containers exposing ports 3000 or similar.
• ss -tuln | grep :3000 or netstat -tuln | grep :3000 — check listening sockets on a host (requires privileges).

• Probe the admin path without invoking the POST shutdown (safe):
• curl -sI http://<host>:<port>/.admin/stop` — issue an HTTP HEAD; this should not trigger the POST handler. If it responds 200/202 on HEAD, do not proceed with POST unless you intend to stop the service.

flowchart TD
  A[Operator runs `tsp-spector serve` on host/container] --> B[Server listens on 0.0.0.0:3000]
  B --> C[Router mounts admin routes at /.admin/stop]
  D[Attacker (network-reachable)] -->|HTTP POST /.admin/stop| C
  C --> E[Handler logs and responds 202, then calls process.exit(0)]
  E --> F[Server process exits -> denial of service]
  style A fill:#f9f,stroke:#333,stroke-width:1px
  style D fill:#fee,stroke:#900,stroke-width:1px
  style F fill:#fcc,stroke:#900,stroke-width:2px