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.
- 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) bypass caused by incomplete localhost detection in the secureFetch function (core/src/shared/secure-fetch.ts:52-54). The code checked for localhost and 127.0.0.1 only, missing IPv6 localhost ([::1]), the full 127.0.0.0/8 loopback range, and 0.0.0.0. An unauthenticated network attacker can craft requests using these undetected localhost addresses to bypass SSRF protections and access internal services. The fix, released in v0.2.136, expands localhost detection to cover all valid loopback addresses and ranges.
Affected products
- asymmetric-effort specifyjs < 0.2.136
Timeline
- 2026-05-29: disclosed
- 2026-05-29: patched: v0.2.136 released