Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2024-43799 send

MEDIUMFix: pillarjs/send@ae4f298

CVE-2024-43799 is a medium-severity (CVSS 5) Cross-site Scripting (XSS) vulnerability in send. A fix is available for send — see the affected versions and patch details below.

send vulnerable to template injection that can lead to XSS

Also known asGHSA-m6fv-jmcg-4jfg
Published
Sep 10, 2024
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-43799.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs44th percentile — riskier than 44% 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.

How urgent is this, really

CVE-2024-43799 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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
130.5Mdownloads / week

Description

Send is a library for streaming files from the file system as a http response. Send passes untrusted user input to SendStream.redirect() which executes untrusted code. This issue is patched in send 0.19.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsendall versions0.19.0npm install send@0.19.0

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

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

  4. How O3 protects you

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

Tailored to CVE-2024-43799. 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
ProductFixed inAdvisory
Discovery 1 for RHEL 9discovery/discovery-server-rhel9:1.12.0-1RHSA-2025:1249
HawtIO 4.0.0 for Red Hat build of Apache Camel 4sendRHSA-2024:11023
NETWORK-OBSERVABILITY-1.7.0-RHEL-9network-observability/network-observability-cli-rhel9:v1.7.0-67RHSA-2024:8014
Red Hat Developer Hub 1.2 on RHEL 9rhdh/rhdh-hub-rhel9:1.2-154RHBA-2024:10184
Red Hat Migration Toolkit for Containers 1.8rhmtc/openshift-migration-ui-rhel8:v1.8.5-7RHSA-2024:10906
Red Hat OpenShift Container Platform 4.17openshift4/nmstate-console-plugin-rhel9:v4.17.0-202501301204.p0.gcffdc60.assembly.stream.el9RHSA-2025:0875
Red Hat OpenShift GitOps 1.12openshift-gitops-1/argocd-rhel8:v1.12.6-2RHSA-2024:8677
Red Hat OpenShift GitOps 1.13openshift-gitops-1/argocd-rhel8:v1.13.2-4RHSA-2024:8581

Frequently Asked Questions

Send is a library for streaming files from the file system as a http response. Send passes untrusted user input to SendStream.redirect() which executes untrusted code. This issue is patched in send 0.19.0.
O3 Security · Impact-Aware SCA

Is CVE-2024-43799 in your dependencies?

O3 Security finds CVE-2024-43799 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-43799: send (Medium 5) | O3 Security