Prototype Pollution Vulnerability in node-extend

node-extend Updated 02 Oct 2025

Summary

01/02/2019
N/A
Yes i
Critical
9.8

CVE-2018-16492: A prototype pollution vulnerability was found in module extend. Affects node-extend versions < 3.0.2-1. Fixed in 3.0.2-1. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

node-extend is a package in the Debian ecosystem that provides a set of utility functions for extending objects. It allows developers to add properties and methods to existing objects. However, a vulnerability has been discovered in versions prior to 3.0.2-1 that allows an attacker to inject arbitrary properties onto Object.prototype.

Vulnerability Detail

The vulnerability, known as CVE-2018-16492, is a prototype pollution vulnerability. It occurs when untrusted user input is used to modify the prototype of an object. In the case of node-extend, an attacker can exploit this vulnerability to inject arbitrary properties onto Object.prototype. This can lead to various security issues, such as the ability to overwrite existing properties or execute arbitrary code.

How To Fix

Minimum fixed version

3.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-extend

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

Workaround

There is no known workaround for this vulnerability. It is recommended to update the package to the fixed version as soon as possible.

Conclusion

In conclusion, the node-extend package in the Debian ecosystem is vulnerable to a prototype pollution vulnerability. It is recommended to update the package to version 3.0.2-1 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for node-extend →

Share this vulnerability

FAQ

Prototype pollution is a vulnerability that occurs when untrusted user input is used to modify the prototype of an object. This can lead to various security issues, such as the ability to overwrite existing properties or execute arbitrary code.

An attacker can exploit this vulnerability by injecting arbitrary properties onto Object.prototype using the node-extend package. This can lead to security issues such as property overwriting or arbitrary code execution.

Yes, a fix is available for this vulnerability. It is recommended to update node-extend to version 3.0.2-1 or later.

Yes, all versions of node-extend prior to 3.0.2-1 are affected by this vulnerability.

Yes, the CVSS score for this vulnerability is 9.8, indicating a critical severity.

Related vulnerabilities

Recent vulnerabilities recorded for node-extend.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

3.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-extend

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