How severe is CVE-2014-6394?

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

Which packages are affected by CVE-2014-6394?

CVE-2014-6394 affects the following packages: send (npm). Ecosystems affected: npm.

How do I fix CVE-2014-6394?

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

How do I detect CVE-2014-6394 in my npm dependencies?

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

How do I mitigate CVE-2014-6394 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

Yes. There are 1 known exploit references for CVE-2014-6394, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-6394?

CVE-2014-6394 has an EPSS (Exploit Prediction Scoring System) score of 4.3%, placing it in the 91th 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-6394?

CVE-2014-6394 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-6394 published, and has it been updated?

CVE-2014-6394 was published on October 8, 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-6394 — send

Fix: visionmedia/send#59

CVE-2014-6394 is a Path Traversal vulnerability in send. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for send — see the affected versions and patch details below.

Directory Traversal in send

Also known asGHSA-xwg4-93c6-3h42

Published

Oct 8, 2014

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

4.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% 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.

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

sendnpm

98.9Mdownloads / week

Description

Versions 0.8.3 and earlier of send are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory.

For example, static(_dirname + '/public') would allow access to _dirname + '/public-restricted'.

Recommendation

Update to version 0.8.4 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`send`	all versions	0.8.4`npm install send@0.8.4`

Affected Products

3 products · 8 configurations

Application

xcodeapple

1 version

7.0

fedorafedoraproject

3 versions

192021

Application

node.jsjoyent

≤ 0.8.3

3 versions

0.8.00.8.10.8.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

visionmedia send before 0.8.4 for Node.js uses a partial comparison for …

github.comNVDSep 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for send, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update send to 0.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-6394 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Versions 0.8.3 and earlier of `send` are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory. For example, `static(_dirname + '/public')` would allow access to `_dirname + '/public-restricted'`. ## Recommendation Update to version 0.8.4 or later.

O3 Security · Impact-Aware SCA

Is CVE-2014-6394 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works