How severe is GHSA-jjv7-qpx3-h62q?

No CVSS score has been assigned to GHSA-jjv7-qpx3-h62q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jjv7-qpx3-h62q?

GHSA-jjv7-qpx3-h62q affects the following packages: qs (npm). Ecosystems affected: npm.

How do I fix GHSA-jjv7-qpx3-h62q?

Update qs to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjv7-qpx3-h62q is resolved across your whole dependency graph.

How do I detect GHSA-jjv7-qpx3-h62q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jjv7-qpx3-h62q if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-jjv7-qpx3-h62q actively exploited in the wild?

No public exploit code has been indexed for GHSA-jjv7-qpx3-h62q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jjv7-qpx3-h62q?

GHSA-jjv7-qpx3-h62q has an EPSS (Exploit Prediction Scoring System) score of 8.3%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jjv7-qpx3-h62q?

GHSA-jjv7-qpx3-h62q is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jjv7-qpx3-h62q published, and has it been updated?

GHSA-jjv7-qpx3-h62q was published on October 24, 2017 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-jjv7-qpx3-h62q — qs

Fix: raymondfeng/node-querystring@43a604b

GHSA-jjv7-qpx3-h62q is a CWE-399 vulnerability in qs. A fix is available for qs — see the affected versions and patch details below.

Denial-of-Service Memory Exhaustion in qs

Also known asCVE-2014-7191

Published

Oct 24, 2017

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

19Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

qsnpm

212.5Mdownloads / week

Description

Versions prior to 1.0 of qs are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.

Recommendation

Update to version 1.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`qs`	all versions	1.0.0`npm install qs@1.0.0`

Affected Products

1 product · 1 configurations

Application

node.jsnodejs

≤ 0.10.18

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update qs to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjv7-qpx3-h62q is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This package is not shipped with any versions of Red Hat Enterprise Linux. Red Hat Software Collections Library components shipping in version 2.2 are affected.

Product	Fixed in	Advisory
Red Hat Software Collections for Red Hat Enterprise Linux 6	`nodejs010-node-gyp-0:3.2.0-3.el6`	RHSA-2016:1380

Frequently Asked Questions

Versions prior to 1.0 of `qs` are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing. ## Recommendation Update to version 1.0.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-jjv7-qpx3-h62q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works