Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 4, published 2 July 2026.
- Which products and versions are affected?
- Asymmetric Effort Specifyjs <0.2.136; @asymmetric-effort/specifyjs (npm) SEMVER:introduced=0,fixed=0.2.136.
- Is there a fix for This vulnerability?
- Yes. @asymmetric-effort/specifyjs (npm): upgrade to 0.2.136 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Asymmetric Effort Specifyjs or @asymmetric-effort/specifyjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @asymmetric-effort/specifyjs (npm): upgrade to 0.2.136 or later
npm install @asymmetric-effort/specifyjs@0.2.136
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) via HTTP redirect in the secureFetch function located in core/src/shared/secure-fetch.ts. The assertSecureUrl validation only checks the initial request URL but does not validate redirect targets; the fetch() API follows redirects by default (up to 20 hops). An attacker can craft a response that redirects from a validated HTTPS URL to an internal service (e.g., http://internal-service/) or other unvalidated destination, causing the application to make requests to unintended targets. The fix, implemented in v0.2.136, changes the default behavior to redirect: 'error' which rejects any redirect, while allowing callers to explicitly opt into following redirects via { redirect: 'follow' } if they trust the target.
Affected products
- asymmetric-effort specifyjs <0.2.136
Timeline
- 2026-07-02: disclosed
- 2026-05-29: patched: Fixed in v0.2.136