{"answers":{"affected":"2 open source packages ship an affected version, including @phun-ky/defaults-deep.","exploited":"There is no known exploitation of CVE-2026-54737 in the wild and no public exploit code.","fix":"Upgrade @phun-ky/defaults-deep to 2.0.5 or later.","what":"CVE-2026-54737 is a high-severity vulnerability in phun-ky defaults-deep, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54737 and fix it if it is affected.\n\nWhat it is: CVE-2026-54737 is a high-severity vulnerability in phun-ky defaults-deep, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54737 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @phun-ky/defaults-deep (npm): affected all versions; fixed in 2.0.5\n- @phun-ky/defaults-deep (npm): affected all versions; fixed in 2.0.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54737/ (Markdown: https://insights.sbomify.com/CVE-2026-54737/index.md)","id":"CVE-2026-54737","markdown":"https://insights.sbomify.com/CVE-2026-54737/index.md","name":"CVE-2026-54737","record":{"aliases":["GHSA-mj3g-7xcc-x4vh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in defaults-deep allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"@phun-ky/defaults-deep is a library like lodash defaultsDeep with array preservation and no lodash dependency. Prior to 2.0.5, defaultsDeep() recursively merges user-supplied objects without filtering proto, constructor, and prototype, allowing properties to be written to Object.prototype. This issue is fixed in version 2.0.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@phun-ky/defaults-deep Has a Prototype Pollution issue via Unsafe Recursive Property Merging","id":"CVE-2026-54737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Lemmy: Rate limit bypass via X-Forwarded-For header spoofing in actix-web ConnectionInfo","id":"CVE-2026-54738"},"packages":[{"ecosystem":"npm","fixed":["2.0.5"],"introduced":["0"],"last_affected":[],"package":"@phun-ky/defaults-deep","purl":null,"source":"GHSA-mj3g-7xcc-x4vh"},{"ecosystem":"npm","fixed":["2.0.5"],"introduced":["0"],"last_affected":[],"package":"@phun-ky/defaults-deep","purl":"pkg:npm/%40phun-ky/defaults-deep","source":"GHSA-mj3g-7xcc-x4vh"}],"prev":{"headline":"Phalcon: Non-constant-time HMAC verification in `Encryption\\Crypt::decrypt` (timing side-channel)","id":"CVE-2026-54736"},"products":["defaults-deep"],"published":"2026-07-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-31","vendors":["phun-ky"]},"summary":"Prototype pollution in defaults-deep allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-54737/"}