@asymmetric-effort/specifyjs: Localhost bypass incomplete (IPv6, 0.0.0.0, 127.x range)

published 2026-07-02 4mo ago modified 2026-09-10 2mo ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

## Finding

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

The localhost exception allowed `localhost` and `127.0.0.1` but did not cover `0.0.0.0`, `[::1]` (IPv6 localhost), or the full `127.0.0.0/8` loopback range.

## Status

**Fixed in v0.2.136** — Localhost detection now covers `localhost`, `127.0.0.1`, `[::1]`, `0.0.0.0`, and the full `127.x.x.x` range.

Patch / fix

fixed in 1 links 2

npm @asymmetric-effort/specifyjs 0.2.136

Is GHSA-xw57-23p8-9wc5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	@asymmetric-effort/specifyjs	<0.2.136	0.2.136

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

Sources

GitHub Advisory GHSA-xw57-23p8-9wc5

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.