@theecryptochad/merge-guard has Prototype Pollution
Affects @theecryptochad/merge-guardSource GCVE Database
CVSS 7.5 High : upgrade to 1.0.1 soon.
Data as of 27 Oct 2026, 00:42 UTC
- Patch
- Available – fixed in 1.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWhat to do
Upgrade @theecryptochad/merge-guard to 1.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@theecryptochad/merge-guard | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to @theecryptochad/merge-guard version 1.0.1 or later, which includes a fix that blocks merging of reserved keys such as __proto__, constructor, and prototype. This official fix prevents prototype pollution via the deepMerge() function. No additional mitigation is required once the upgrade is applied.
Description
@theecryptochad/merge-guard versions prior to 1.0.1 contain a Prototype Pollution vulnerability in the deepMerge() function. This occurs because the function merges objects without filtering out special keys like __proto__, allowing an attacker to modify Object.prototype. This can lead to privilege escalation and application logic bypass when untrusted input is merged.