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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.

Published by the source

2 Jul 2026, 19:08 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j5qp-p44g-2m49

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j5qp-p44g-2m49

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

# Patch Next advisory brief: GHSA-j5qp-p44g-2m49

Advisory: @asymmetric-effort/specifyjs: No redirect target validation in secureFetch
IDs: GHSA-j5qp-p44g-2m49
Record: https://patchnext.com/advisories/ghsa-j5qp-p44g-2m49 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @asymmetric-effort/specifyjs 0.2.136. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @asymmetric-effort/specifyjs: affected < 0.2.136; fixed in 0.2.136

## Suggested inspection (read-only)
- `npm ls @asymmetric-effort/specifyjs --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 @asymmetric-effort/specifyjs.
- 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://osv.dev/vulnerability/GHSA-j5qp-p44g-2m49 (OSV record GHSA-j5qp-p44g-2m49 lists affected ranges: npm @asymmetric-effort/specifyjs >=0 <0.2.136 (fixed))
- Verified: https://github.com/advisories/GHSA-j5qp-p44g-2m49 (GitHub-reviewed advisory GHSA-j5qp-p44g-2m49 lists affected ranges: npm @asymmetric-effort/specifyjs >=0 <0.2.136)

Commands are suggestions: review each one before running it.