CVE-2021-23417: Prototype Pollution in deepmergefn

deepmergefn Updated 02 Oct 2025

Summary

10/08/2021
No i
Moderate
5.6

CVE-2021-23417: Prototype Pollution in deepmergefn. Affects deepmergefn versions < 1.1.0. 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 deepmergefn package is an npm package that provides a deep merging functionality for JavaScript objects. It allows developers to merge multiple objects into a single object, recursively merging nested properties. This package is widely used in JavaScript applications for managing complex object structures. However, all versions of deepmergefn are vulnerable to Prototype Pollution via the deepMerge function.

Vulnerability Detail

Prototype Pollution is a vulnerability that occurs when an attacker can inject or modify properties of an object's prototype. In the case of deepmergefn, the deepMerge function does not properly sanitize user input, allowing an attacker to modify the prototype of an object. This can lead to various security issues, such as arbitrary code execution, denial of service, or data manipulation. The impact of this vulnerability depends on how the affected package is used in the application and the privileges of the user running the application.

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

If updating the package is not immediately possible, a temporary workaround is to avoid using the deepMerge function with untrusted input. Developers should carefully validate and sanitize any user input before passing it to the deepMerge function. Additionally, it is recommended to review the usage of deepmergefn in the application and consider alternative libraries or custom implementations that do not have the Prototype Pollution vulnerability.

Conclusion

The deepmergefn package is vulnerable to Prototype Pollution via the deepMerge function. It is recommended to update the package to version 1.1.1 or later to fix this vulnerability. If immediate updating is not possible, developers should validate and sanitize user input before using the deepMerge function. Consideration should also be given to alternative libraries or custom implementations that do not have the Prototype Pollution vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for deepmergefn →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that allows an attacker to modify an object's prototype, leading to potential security issues.

The deepmergefn package uses the deepMerge function to merge multiple objects into a single object, recursively merging nested properties.

The consequences of the Prototype Pollution vulnerability in deepmergefn can include arbitrary code execution, denial of service, or data manipulation.

Yes, the maintainers of deepmergefn have released a fix in version 1.1.1.

Yes, developers can consider alternative libraries or custom implementations that do not have the Prototype Pollution vulnerability.

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