npm package report

Is deepmerge safe?

1 known vulnerability, worst severity LOW.

// reach

1 direct dependencies

none carry a known advisory

    224 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

    cvss
    5.3
    medium

    CVSS v3.1 base score out of 10; GitHub rates it LOW

    epss
    0.51%
    medium

    chance of exploitation in 30 days, 44th percentile of all CVEs

    xyz score
    2.5
    low

    CyberXYZ composite out of 10

    fig. 01 — GHSA-gcqx-w48m-w2h4, the advisory selected below

    // 1 advisories

    GHSA-gcqx-w48m-w2h4

    LOWGitHub ratingCVE-2026-93753

    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.

    // cvss v3.1 vector

    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

    Attack vector
    Network
    Attack complexity
    Low
    Privileges required
    None
    User interaction
    None
    Scope
    Unchanged
    Confidentiality
    None
    Integrity
    Low
    Availability
    None

    Checked 2026-11-06 at 21:39 UTC. The most recent advisory here was published 2026-09-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.