Skip to content
OpenAdvisories
Medium GHSA-j5qp-p44g-2m49

@asymmetric-effort/specifyjs: No redirect target validation in secureFetch

Published Jul 2, 2026 · Updated Sep 10, 2026 · Assigned by GHSA

Description

## Finding

**Location**: `core/src/shared/secure-fetch.ts`

`assertSecureUrl` validated only the initial request URL. The `fetch()` API follows redirects by default (up to 20 hops). A request to a valid `https://` URL could redirect to `http://internal-service/` or other unvalidated destinations.

## Status

**Fixed in v0.2.136** — `secureFetch` now defaults to `redirect: 'error'` which rejects any redirect. Callers can override with `{ redirect: 'follow' }` if they trust the target.

Affected packages

EcosystemPackageAffectedFixedRecord
npm @asymmetric-effort/specifyjs < 0.2.136 0.2.136 GHSA-j5qp-p44g-2m49

References