What is GHSA-XW57-23P8-9WC5?

GHSA-XW57-23P8-9WC5 is a medium-severity server-side request forgery (SSRF) vulnerability in @asymmetric-effort/specifyjs (npm), affecting versions < 0.2.136. It is fixed in 0.2.136. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of @asymmetric-effort/specifyjs are affected by GHSA-XW57-23P8-9WC5?

@asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.

Is there a fix for GHSA-XW57-23P8-9WC5?

Yes. GHSA-XW57-23P8-9WC5 is fixed in 0.2.136. Upgrade to this version or later.

Is GHSA-XW57-23P8-9WC5 exploitable, and should I be worried?

Whether GHSA-XW57-23P8-9WC5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-XW57-23P8-9WC5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-XW57-23P8-9WC5 in @asymmetric-effort/specifyjs

Q: Which versions of @asymmetric-effort/specifyjs are affected by GHSA-XW57-23P8-9WC5?

@asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.

Q: Is there a fix for GHSA-XW57-23P8-9WC5?

Yes. GHSA-XW57-23P8-9WC5 is fixed in 0.2.136. Upgrade to this version or later.

Q: Is GHSA-XW57-23P8-9WC5 exploitable, and should I be worried?

Whether GHSA-XW57-23P8-9WC5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-XW57-23P8-9WC5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-XW57-23P8-9WC5?

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

Summary

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

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.

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

@asymmetric-effort/specifyjs (< 0.2.136)

Security releases

@asymmetric-effort/specifyjs → 0.2.136 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-XW57-23P8-9WC5? GHSA-XW57-23P8-9WC5 is a medium-severity server-side request forgery (SSRF) vulnerability in @asymmetric-effort/specifyjs (npm), affecting versions < 0.2.136. It is fixed in 0.2.136. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of @asymmetric-effort/specifyjs are affected by GHSA-XW57-23P8-9WC5? @asymmetric-effort/specifyjs (npm) versions < 0.2.136 is affected.
Is there a fix for GHSA-XW57-23P8-9WC5? Yes. GHSA-XW57-23P8-9WC5 is fixed in 0.2.136. Upgrade to this version or later.
Is GHSA-XW57-23P8-9WC5 exploitable, and should I be worried? Whether GHSA-XW57-23P8-9WC5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-XW57-23P8-9WC5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-XW57-23P8-9WC5? Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.

Other vulnerabilities in @asymmetric-effort/specifyjs

CVE-IDSeverityPackage summary