deepmerge

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 1LowAffects 1 version
Severity distribution (all time)
1vulnerability
  • Critical0 (0.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low1 (100.0%)

Monthly breakdown

  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 1

Vulnerabilities (1)

Known vulnerabilities affecting deepmerge, based on data from OSV.

Vulnerabilities affecting deepmerge
IDSeveritySummaryAffected versionsPublishedSource
GHSA-gcqx-w48m-w2h4Lowdeepmerge mergeObject() allows prototype poisoning of returned objectsdeepmerge through 4.3.1 contains a prototype poisoning vulnerability in the mergeObject() function that fails to properly validate keys being written to target objects. Attackers can supply malicious source objects in merge operations to inject attacker-controlled properties into the returned object's prototype, causing applications to inherit unintended values when accessing properties without own-property checks.
  • >= 4.2.0, <= 4.3.1
GitHub (opens in a new tab)
  • GHSA-gcqx-w48m-w2h4Low
    deepmerge mergeObject() allows prototype poisoning of returned objects
    • >= 4.2.0, <= 4.3.1

    deepmerge through 4.3.1 contains a prototype poisoning vulnerability in the mergeObject() function that fails to properly validate keys being written to target objects. Attackers can supply malicious source objects in merge operations to inject attacker-controlled properties into the returned object's prototype, causing applications to inherit unintended values when accessing properties without own-property checks.

    CVE: CVE-2026-93753

Showing 1-1 of 1 vulnerabilities