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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2014-6394 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-6394?

O3 pinpoints whether CVE-2014-6394 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 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

CVE-2014-6394

CVE-2014-6394 is a Path Traversal vulnerability in send. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2014-6394 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

sendnpm

138.4Mdownloads / week

Description

visionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using "public-restricted" under a "public" directory.

Affected Packages

1 total 1 fixed

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether CVE-2014-6394 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-6394 in your dependencies?

O3 detects CVE-2014-6394 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works