How severe is GHSA-f9cm-p3w6-xvr3?

No CVSS score has been assigned to GHSA-f9cm-p3w6-xvr3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f9cm-p3w6-xvr3?

GHSA-f9cm-p3w6-xvr3 affects the following packages: qs (npm). Ecosystems affected: npm.

How do I fix GHSA-f9cm-p3w6-xvr3?

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

How do I detect GHSA-f9cm-p3w6-xvr3 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-f9cm-p3w6-xvr3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f9cm-p3w6-xvr3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f9cm-p3w6-xvr3 can be triaged on real exposure rather than presence alone.

Is GHSA-f9cm-p3w6-xvr3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f9cm-p3w6-xvr3 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-f9cm-p3w6-xvr3?

GHSA-f9cm-p3w6-xvr3 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th 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-f9cm-p3w6-xvr3?

GHSA-f9cm-p3w6-xvr3 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-399 (CWE-399). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f9cm-p3w6-xvr3 published, and has it been updated?

GHSA-f9cm-p3w6-xvr3 was published on October 9, 2018 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-f9cm-p3w6-xvr3 — qs

GHSA-f9cm-p3w6-xvr3 is a Uncontrolled Resource Consumption vulnerability in qs. A fix is available for qs — see the affected versions and patch details below.

Denial-of-Service Extended Event Loop Blocking in qs

Also known asCVE-2014-10064

Published

Oct 9, 2018

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

140.5Mdownloads / week

Description

The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring.

Affected Packages

1 total 1 fixed

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

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-f9cm-p3w6-xvr3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f9cm-p3w6-xvr3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f9cm-p3w6-xvr3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions prior to 1.0.0 of `qs` are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string. ## Recommendation Update to version 1.0.0 or later

O3 Security · Impact-Aware SCA

Is GHSA-f9cm-p3w6-xvr3 in your dependencies?

O3 Security finds GHSA-f9cm-p3w6-xvr3 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works