Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

TypeSpec: Unauthenticated Remote Shutdown of Spector Mock Server via POST /.admin/stop

GHSA-7q9c-hpx7-9cwm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@typespec/spector 0.1.0-alpha.27), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary @typespec/spector registers a POST /.admin/stop HTTP route with no authentication, authorization token, Origin check, or IP-source restriction. Any network-reachable client can send a single unauthenticated POST request to terminate the mock server process. Because the server binds to 0.0.0.0 by default (all interfaces), this endpoint is exposed to any host that can reach the server's port—not just localhost—making a complete denial-of-service trivially achievable with one HTTP request. Severity is High (CVSS 7.5). Details The vulnerability originates in packages/spector/src/routes/admin.ts at line 7, where an Express router registers the shutdown endpoint with no authentication middleware whatsoever: The constant AdminUrls.stop resolves to /.admin/stop (packages/spector/src/constants.ts:1-3). The complete attack-reachable call chain is: 1. packages/spector/src/cli/cli.ts:139-166 — tsp-spector serve <scenariosPaths.. starts the server on default port 3000. No host option is…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7q9c-hpx7-9cwm

  2. Revision 2 · amended ·

    Amended from osv record GHSA-7q9c-hpx7-9cwm

  3. Revision 1 · created ·

    Published from ghsa record GHSA-7q9c-hpx7-9cwm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7q9c-hpx7-9cwm

Advisory: TypeSpec: Unauthenticated Remote Shutdown of Spector Mock Server via POST /.admin/stop
IDs: GHSA-7q9c-hpx7-9cwm
Record: https://patchnext.com/advisories/ghsa-7q9c-hpx7-9cwm (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @typespec/spector 0.1.0-alpha.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @typespec/spector: affected <= 0.1.0-alpha.26; fixed in 0.1.0-alpha.27

## Suggested inspection (read-only)
- `npm ls @typespec/spector --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @typespec/spector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7q9c-hpx7-9cwm (GitHub-reviewed advisory GHSA-7q9c-hpx7-9cwm lists affected ranges: npm @typespec/spector >=0 <=0.1.0-alpha.26)
- Verified: https://osv.dev/vulnerability/GHSA-7q9c-hpx7-9cwm (OSV record GHSA-7q9c-hpx7-9cwm lists affected ranges: npm @typespec/spector >=0 <0.1.0-alpha.27 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…