# GHSA-j5qp-p44g-2m49: @asymmetric-effort/specifyjs: No redirect target validation in secureFetch

> Attackers can exploit unvalidated redirects in secureFetch to access internal services, bypassing URL validation controls.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2026

## What is GHSA-j5qp-p44g-2m49?

GHSA-j5qp-p44g-2m49 is a server-side request forgery vulnerability in @asymmetric-effort/specifyjs, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-j5qp-p44g-2m49?

2 open source packages ship an affected version, including @asymmetric-effort/specifyjs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@asymmetric-effort/specifyjs` | npm | All versions | 0.2.136 |
| `@asymmetric-effort/specifyjs` | npm | All versions | 0.2.136 |

## How do I fix GHSA-j5qp-p44g-2m49?

Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.

## Is GHSA-j5qp-p44g-2m49 being exploited?

There is no known exploitation of GHSA-j5qp-p44g-2m49 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j5qp-p44g-2m49 and fix it if it is affected.

What it is: GHSA-j5qp-p44g-2m49 is a server-side request forgery vulnerability in @asymmetric-effort/specifyjs, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-j5qp-p44g-2m49 in the wild and no public exploit code.

Affected packages and fixed versions:
- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.136
- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.136

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-j5qp-p44g-2m49/ (Markdown: https://insights.sbomify.com/GHSA-j5qp-p44g-2m49/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j5qp-p44g-2m49

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j5qp-p44g-2m49/
Summaries are generated and may contain mistakes; the official description above is the record.