CVE-2015-8859: Root Path Disclosure in send

send Updated 02 Oct 2025

Summary

24/10/2017
Yes i
Moderate
5.3

CVE-2015-8859: Root Path Disclosure in send. Affects send versions < 0.11.1. Fixed in 0.11.1. How to fix ↓

Also tracked for

The same CVE-2015-8859 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'send' package is an npm module used for serving static files over HTTP. It provides functionality to send files from the server to the client. This package is widely used in web applications to handle file transfers. However, versions prior to 0.11.2 are affected by an information leakage vulnerability. This vulnerability allows an attacker to enumerate paths on the server filesystem, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability in the 'send' package allows an attacker to discover the paths on the server filesystem. By exploiting this vulnerability, an attacker can gain insights into the server's directory structure and potentially access sensitive files. This information disclosure can be used to plan further attacks or exploit other vulnerabilities. The vulnerability has a CVSSv3 score of 5.3, indicating a moderate severity level.

How To Fix

Latest published version: 1.2.1 as of 22 Oct 2026

npm install send@1.2.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.11.1

This is the first release that contains the fix.

npm install send@0.11.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The best course of action is to update the package to the latest version as mentioned in the 'how_to_fix' section.

Conclusion

The 'send' package prior to version 0.11.2 is affected by an information leakage vulnerability that allows an attacker to enumerate paths on the server filesystem. To mitigate this vulnerability, it is crucial to update the package to version 0.11.1 or later. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for send →

Share this vulnerability

FAQ

The vulnerability allows an attacker to enumerate paths on the server filesystem, potentially exposing sensitive information. This information can be used for further attacks or exploitation of other vulnerabilities.

You can use Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json.

Yes, the CVSSv3 score for this vulnerability is 5.3, indicating a moderate severity level.

There are no known exploits mentioned specifically for this vulnerability. However, it is always recommended to update to the latest version to mitigate any potential risks.

To fix this vulnerability, it is recommended to update the 'send' package to version 0.11.1 or later.

Related vulnerabilities

Recent vulnerabilities recorded for send.

How To Fix

Latest published version: 1.2.1 as of 22 Oct 2026

npm install send@1.2.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.11.1

This is the first release that contains the fix.

npm install send@0.11.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback