CVE-2022-25352: Prototype Pollution in libnested

libnested Updated 02 Oct 2025

Summary

18/03/2022
Yes i
Critical
9.8

CVE-2022-25352: Prototype Pollution in libnested. Affects libnested versions < 1.5.2. Fixed in 1.5.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libnested is an npm package that provides nested object manipulation utilities. It allows users to perform various operations on nested objects, such as setting values, getting values, and merging objects. The package is widely used in JavaScript applications for handling complex data structures. However, versions of libnested before 1.5.2 are vulnerable to a Prototype Pollution attack.

Vulnerability Detail

The vulnerability in libnested arises from the set function in index.js. It is a result of an incomplete fix for a previous vulnerability (CVE-2020-28283). Prototype Pollution is a type of vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior in the application. In the case of libnested, an attacker can manipulate the prototype of a nested object, potentially causing data corruption, privilege escalation, or remote code execution.

How To Fix

Minimum fixed version

1.5.2

This is the first release that contains the fix.

npm install libnested@1.5.2

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 crucial to update to the fixed version of libnested to mitigate the risk of exploitation.

Conclusion

The libnested package before version 1.5.2 is vulnerable to Prototype Pollution. It is crucial for developers to update to the fixed version to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libnested →

Share this vulnerability

FAQ

libnested is an npm package that provides nested object manipulation utilities.

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior in the application.

The impact of this vulnerability can range from data corruption to privilege escalation or remote code execution.

To fix this vulnerability, update libnested to version 1.5.2 or later.

There is no known workaround for this vulnerability. Updating to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for libnested.

How To Fix

Minimum fixed version

1.5.2

This is the first release that contains the fix.

npm install libnested@1.5.2

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