CVE-2024-29409 is a medium-severity (CVSS 5.5) Code Injection vulnerability in @nestjs/common. A fix is available for @nestjs/common — see the affected versions and patch details below.
nest allows a remote attacker to execute arbitrary code via the Content-Type header
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-29409.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
@nestjs/commonnpmDescription
File Upload vulnerability in nestjs nest prior to v.11.0.16 allows a remote attacker to execute arbitrary code via the Content-Type header.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @nestjs/common | ≥ 11.0.0-next.1&&< 11.0.16 | 11.0.16npm install @nestjs/common@11.0.16 |
| 📦npm | @nestjs/common | all versions | 10.4.16npm install @nestjs/common@10.4.16 |
Affected Products
nestnestjsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nestjs/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nestjs/common to 11.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-29409 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2024-29409 in your dependencies?
Find it across npm, including transitive dependencies.