Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@phun-ky/defaults-deep

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.3npmPublished

    @phun-ky/defaults-deep Has a Prototype Pollution issue via Unsafe Recursive Property Merging

    CVE-2026-54737 · GHSA-mj3g-7xcc-x4vh

    Affected
    • npm @phun-ky/defaults-deep < 2.0.5
    Fixed in
    2.0.5· Vendor fix available
    Issue
    Impact A prototype pollution vulnerability exists in @phun-ky/defaults-deep prior to version 2.0.5. The library recursively merged user-supplied objects without filtering unsafe property names such as proto, constructor, and prototype. An attacker able to supply crafted input could cause properties to be written to Object.prototype, resulting in prototype pollution affecting all objects within the running process. Applications that pass untrusted input to defaultsDeep() may be impacted. Depending on how the application uses merged objects, this could lead to unexpected behavior, logic bypasses, denial of service, or other security issues. Patches This issue has been fixed in version 2.0.5. Users should upgrade to version 2.0.5 or later. The fix prevents unsafe prototype-related keys (proto, constructor, and prototype) from being processed during recursive merge operations and includes regression tests covering known prototype pollution vectors. Workarounds Users unable to upgrade…

    Recommended action: Upgrade to 2.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →