CVE-2026-54737

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@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.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

July 31, 2026

Last Modified

July 31, 2026

Advisory Details (4)

Auto-updated Jul 31, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

Release 2.0.5

Patch available: phun-ky/defaults-deep 2.0.5

https://github.com/phun-ky/defaults-deep/releases/tag/2.0.5
github_commit Patch Available

commit 807dba930f87 (phun-ky/defaults-deep)

Patch available: phun-ky/defaults-deep 2.0.5 (contains commit 807dba930f87)

https://github.com/phun-ky/defaults-deep/commit/807dba930f8718f9126cad59d949b8fd3539b059
github_pr Patch Available

Mitigate prototype pollution vulnerability

Patch available: phun-ky/defaults-deep 2.0.5 (PR #49 merged 2026-06-08)

https://github.com/phun-ky/defaults-deep/pull/49
github Patch Available

Prototype Pollution in @phun-ky/defaults-deep via Unsafe Recursive Property Merging · Advisory · phun-ky/defaults-deep · GitHub

Affected: version 2.0.5.

https://github.com/phun-ky/defaults-deep/security/advisories/GHSA-mj3g-7xcc-x4vh

Vendor Advisories for CVE-2026-54737(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@phun-ky/defaults-deep—2.0.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 00:11 UTCEG score recompute
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 23:54 UTCEG score recompute
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 23:40 UTCEG score recompute
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 23:25 UTCEG score recompute
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 11:18 UTCEG score recompute
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 11:04 UTCEG score recompute
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-13 22:42 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 22:27 UTCEG score recompute
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 22:11 UTCEG score recompute
  18. 2026-08-11 10:02 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 21:40 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 21:26 UTCEG score recompute
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 21:11 UTCEG score recompute
  25. 2026-08-06 20:57 UTCEG score recompute
Show 15 more
  1. 2026-08-06 13:47 UTCEPSS rescore
  2. 2026-08-05 20:42 UTCEG score recompute
  3. 2026-08-05 19:17 UTCEPSS rescore
  4. 2026-08-04 20:28 UTCEG score recompute
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:39 UTCEPSS rescore
  7. 2026-08-03 20:09 UTCEG score recompute
  8. 2026-08-03 10:36 UTCEPSS rescore
  9. 2026-08-02 07:47 UTCEG score recompute
  10. 2026-08-02 02:27 UTCEPSS rescore
  11. 2026-07-31 19:23 UTCEG score recompute
  12. 2026-07-31 19:08 UTCEG score recompute
  13. 2026-07-31 18:19 UTCEG score recompute
  14. 2026-07-31 18:04 UTCEG score recompute
  15. 2026-07-31 18:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54737?
CVE-2026-54737 is a high vulnerability published on July 31, 2026. @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…
When was CVE-2026-54737 disclosed?
CVE-2026-54737 was first published in the National Vulnerability Database on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54737 actively exploited?
CVE-2026-54737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54737?
CVE-2026-54737 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-54737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54737, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54737

Explore →

Is Your Infrastructure Affected by CVE-2026-54737?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs