Critical HTTP Request Smuggling Vulnerability in Node.js Package

nodejs Updated 03 Oct 2025

Summary

07/04/2016
N/A
No i
High
7.5

UBUNTU-CVE-2016-2086: Node.js 0.10.x before 0.10.42, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allow remote attackers to conduct HTTP request smuggling attacks via a crafted Content-Length HTTP header. Affects nodejs versions 0.10.15~dfsg1-4 – 0.10.25~dfsg2-2ubuntu1.2+esm2. No fix is published. How to fix ↓

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

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

Node.js is a popular open-source runtime environment that allows developers to execute JavaScript code server-side. It is widely used for building scalable network applications. The affected versions of Node.js, specifically 0.10.x, 0.12.x, 4.x, and 5.x, have a vulnerability that can be exploited by remote attackers to conduct HTTP request smuggling attacks, compromising the integrity of web applications.

Vulnerability Detail

The vulnerability, identified as CVE-2016-2086, allows remote attackers to perform HTTP request smuggling by crafting a malicious Content-Length HTTP header. This can lead to unauthorized access to sensitive data, session hijacking, or even full system compromise. The flaw exists in multiple versions of Node.js prior to their respective patched releases, making it critical for users to address this issue promptly.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can implement additional validation on incoming HTTP headers to mitigate the risk of HTTP request smuggling. This can be done by using middleware in your application to check and sanitize headers before processing requests.

Conclusion

The CVE-2016-2086 vulnerability in Node.js poses a significant risk to applications that utilize affected versions. It is crucial for developers and system administrators to update their Node.js installations to the latest patched versions to mitigate potential security threats.

See every vulnerability recorded for nodejs →

Share this vulnerability

FAQ

CVE-2016-2086 is a vulnerability in Node.js that allows remote attackers to conduct HTTP request smuggling attacks via a crafted Content-Length HTTP header.

The affected versions include Node.js 0.10.x before 0.10.42, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Exploitation of this vulnerability can lead to unauthorized access to sensitive data, session hijacking, and potentially full system compromise.

Yes, there are patched versions available for the affected Node.js packages. Users should update to the latest secure version as outlined in the 'how to fix' section.

Related vulnerabilities

Recent vulnerabilities recorded for nodejs.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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