Prototype Pollution in smart-extend

smart-extend Updated 02 Oct 2025

Summary

02/09/2020
MODERATE
No i
Moderate
Not published

GHSA-f8h3-rqrm-47v9: Prototype Pollution in smart-extend. Affected versions are not published. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The smart-extend package is an npm module that provides a function called deep() which allows for deep merging of objects. It is commonly used in JavaScript applications to merge and extend objects. However, all versions of smart-extend are vulnerable to Prototype Pollution. This vulnerability allows attackers to modify the prototype of the Object, leading to the addition or modification of existing properties that will exist on all objects.

Vulnerability Detail

The Prototype Pollution vulnerability in smart-extend arises from the deep() function. By manipulating the input to this function, an attacker can modify the prototype of the Object, enabling them to add or modify properties that will affect all objects in the application. This can lead to various security issues such as remote code execution, privilege escalation, or data tampering. The severity of this vulnerability is considered moderate.

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 there is no fix available, a possible workaround is to carefully validate and sanitize any user input or data that is passed to the deep() function. By ensuring that only trusted and properly validated data is used, the risk of exploitation can be reduced. Here is an example of how to sanitize the input:

const safeData = validateAndSanitize(userInput);
deep(safeData);

Conclusion

The smart-extend package is vulnerable to Prototype Pollution, which can have serious security implications. Until a fix is available, it is recommended to use an alternative module and ensure proper validation and sanitization of user input. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for smart-extend →

Share this vulnerability

FAQ

smart-extend is an npm module that provides a function called deep() for merging and extending objects in JavaScript applications.

Prototype Pollution is a vulnerability that allows attackers to modify the prototype of an object, leading to the addition or modification of properties that will exist on all objects.

The risks of this vulnerability include remote code execution, privilege escalation, and data tampering.

No, there is currently no fix available for this vulnerability in smart-extend.

One possible workaround is to carefully validate and sanitize user input or data before passing it to the deep() function.

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