Skip to main content
VulnerabilityPublished

@theecryptochad/merge-guard has Prototype Pollution

Affects @theecryptochad/merge-guardSource GCVE Database

0

CVSS 7.5 High : upgrade to 1.0.1 soon.

Data as of 27 Oct 2026, 00:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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:N

What to do

Upgrade @theecryptochad/merge-guard to 1.0.1.

Affected software

ProductAffectedFixed in
npm@theecryptochad/merge-guardAffected
  • <1.0.1
Fixed in
  • 1.0.1

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.

References

Community reviews

Loading reviews…