Vulnerability Database · npm · defaults-deep · Version

defaults-deep 0.2.4

0.2.4 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 07 Feb 2018 Status latest release Licence MIT Also known from other sources 1 Newer releases 8 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

defaults-deep 0.2.4 vulnerabilities

1 vulnerability cover defaults-deep 0.2.4. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2018-16486: Prototype Pollution in defaults-deep 9.8 critical No fix published 07 Feb 2019

Looking for another version, or everything Vulert holds for defaults-deep?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About defaults-deep 0.2.4

Is defaults-deep 0.2.4 vulnerable?

Yes. 1 vulnerability in the Vulert database cover defaults-deep 0.2.4: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 0.2.4 the latest release of defaults-deep?

Yes. 0.2.4 is the current release, published 07 Feb 2018. Staying on the current line is what keeps you inside the publisher's fixes.

How do I monitor defaults-deep for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the defaults-deep version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.