How severe is CVE-2014-7191?

No CVSS score has been assigned to CVE-2014-7191 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-7191?

CVE-2014-7191 affects the following packages: qs (npm). Ecosystems affected: npm.

How do I fix CVE-2014-7191?

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

How do I detect CVE-2014-7191 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 CVE-2014-7191 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 CVE-2014-7191?

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

Is CVE-2014-7191 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-7191 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 CVE-2014-7191?

CVE-2014-7191 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 CVE-2014-7191?

CVE-2014-7191 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 CVE-2014-7191 published, and has it been updated?

CVE-2014-7191 was published on October 19, 2014 and was last updated on April 10, 2026. 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

CVE-2014-7191 — qs

Fix: raymondfeng/node-querystring@43a604b

CVE-2014-7191 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 asGHSA-jjv7-qpx3-h62q

Published

Oct 19, 2014

Updated

Apr 10, 2026

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 ↗

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

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

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`

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 CVE-2014-7191 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 CVE-2014-7191 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-7191. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 CVE-2014-7191 in your dependencies?

O3 Security finds CVE-2014-7191 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