Which versions of querystringify are affected by GHSA-HXCM-V35H-MG2X?

querystringify (npm) versions < 2.0.0 is affected.

Is there a fix for GHSA-HXCM-V35H-MG2X?

Yes. GHSA-HXCM-V35H-MG2X is fixed in 2.0.0. Upgrade to this version or later.

Is GHSA-HXCM-V35H-MG2X exploitable, and should I be worried?

Whether GHSA-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X in querystringify

Q: What is GHSA-HXCM-V35H-MG2X?

GHSA-HXCM-V35H-MG2X is a high-severity security vulnerability in querystringify (npm), affecting versions < 2.0.0. It is fixed in 2.0.0.

Q: Is there a fix for GHSA-HXCM-V35H-MG2X?

Yes. GHSA-HXCM-V35H-MG2X is fixed in 2.0.0. Upgrade to this version or later.

Q: Is GHSA-HXCM-V35H-MG2X exploitable, and should I be worried?

Whether GHSA-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X?

Upgrade querystringify to 2.0.0 or later.

GHSA-HXCM-V35H-MG2X

GHSA-HXCM-V35H-MG2X is a high-severity security vulnerability in querystringify (npm), affecting versions < 2.0.0. It is fixed in 2.0.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Prototype Pollution in querystringify

A vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string.

Impact

Affected versions

querystringify (< 2.0.0)

Security releases

querystringify → 2.0.0 (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 querystringify to 2.0.0 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-HXCM-V35H-MG2X? GHSA-HXCM-V35H-MG2X is a high-severity security vulnerability in querystringify (npm), affecting versions < 2.0.0. It is fixed in 2.0.0.
Which versions of querystringify are affected by GHSA-HXCM-V35H-MG2X? querystringify (npm) versions < 2.0.0 is affected.
Is there a fix for GHSA-HXCM-V35H-MG2X? Yes. GHSA-HXCM-V35H-MG2X is fixed in 2.0.0. Upgrade to this version or later.
Is GHSA-HXCM-V35H-MG2X exploitable, and should I be worried? Whether GHSA-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X 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-HXCM-V35H-MG2X? Upgrade querystringify to 2.0.0 or later.