CVE-2021-28860: Prototype Pollution in mixme

mixme Updated 02 Oct 2025

Summary

10/02/2022
Yes i
Critical
9.1

CVE-2021-28860: Prototype Pollution in mixme. Affects mixme versions < 0.5.1. Fixed in 0.5.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

mixme is an npm package for manipulating JavaScript objects. It provides functions like mutate() and merge() to add or alter properties of an object. However, mixme version 0.5.0 is vulnerable to prototype pollution attacks. By using the 'proto' property, an attacker can modify the prototype of an object, leading to potential denial of service (DoS) attacks.

Vulnerability Detail

The vulnerability in mixme version 0.5.0 allows an attacker to pollute the prototype of objects using the 'proto' property. This pollution affects every object in the program, potentially leading to a DoS attack. The polluted attribute can be directly assigned to all objects, compromising the availability of the program.

How To Fix

Latest published version: 2.0.2 as of 22 Oct 2026

npm install mixme@2.0.2

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.5.1

This is the first release that contains the fix.

npm install mixme@0.5.1

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 essential to update to the fixed version of mixme to mitigate the risk of a DoS attack.

Conclusion

mixme version 0.5.0 is vulnerable to prototype pollution, which can lead to a denial of service attack. It is crucial to update to mixme version 0.5.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for mixme →

Share this vulnerability

FAQ

mixme is an npm package used for manipulating JavaScript objects.

Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior and potential security issues.

The vulnerability in mixme can result in a denial of service (DoS) attack, compromising the availability of the program.

To fix this vulnerability, update mixme to version 0.5.1 or later.

No, there is no known workaround. Updating to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for mixme.

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

Latest published version: 2.0.2 as of 22 Oct 2026

npm install mixme@2.0.2

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.5.1

This is the first release that contains the fix.

npm install mixme@0.5.1

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