npm package
send 0.11.0 vulnerabilities, and the version that fixes all of them
send 0.11.0 has 2 known vulnerabilities; 0.19.0 fixes all of them.
npm (opens in a new tab) describes it as “Better streaming static file server with Range and conditional-GET support”
- Known vulnerabilities
- 2
- None rated high or critical
- Released
- Jan 5, 2015
- Latest is 1.2.1
- Downloads last week
- 184
- Under 1% of send downloads
- Licence
- MIT
- Pulls in
- 12 packages
- Resolved by deps.dev
What to upgrade to
0.19.0 is the closest release with no known vulnerabilities.
Newest 0.11.x release. Released Jan 20, 2015.
1 known vulnerability, worst rated warning0.19.0Upgrade to this
Fixes all 2 known vulnerabilities. Released Sep 10, 2024.
No known vulnerabilitiesLatest release. Released Dec 15, 2025.
No known vulnerabilities
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- WarningVulnerability
2 known vulnerabilities in send 0.11.0
EPSS: top 9%Most serious: CVE-2015-8859, Root Path Disclosure in send. Upgrading to 0.19.0 fixes all of them.
- LowOutdated
send 0.11.0 is 1 major version behind
Latest release is 1.2.1.
Every advisory for send 0.11.0
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
WarningCVE-2015-8859 on OSV.dev (opens in a new tab)GHSA-jgqf-hwc5-hh37EPSS: top 9%
Root Path Disclosure in send
Fixed in 0.11.1. Published Oct 24, 2017.
LowCVE-2024-43799 on OSV.dev (opens in a new tab)GHSA-m6fv-jmcg-4jfgEPSS: top 56%
send vulnerable to template injection that can lead to XSS
Fixed in 0.19.0. Published Sep 10, 2024.
Who is still on a vulnerable send
7% of last week’s 153.5M send downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is send the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly send 0.11.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.