VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

node-deep-extend: vulnerability history, versions and safety

node-deep-extend is a package in the Ubuntu ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-deep-extend vulnerabilities

Vulert verdict on node-deep-extend i

Updated on 23 Oct 2026

Careful: one of the 1 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 1 vulnerability on record across 1 year, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Jul 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i

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 Versions

Which versions are affected

Every version Vulert holds for node-deep-extend, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
0.4.1-1 U1 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for node-deep-extend

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Prototype Pollution Vulnerability in node-deep-extend Package 9.8 critical No fix published 03 Jul 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 node-deep-extend

Is node-deep-extend safe to use?

Vulert records 1 vulnerabilities for node-deep-extend in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does node-deep-extend have?

1 vulnerability is recorded for node-deep-extend in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-deep-extend vulnerabilities disclosed?

0 vulnerabilities were recorded for node-deep-extend in the last 12 months, and the oldest entry in this database dates to 03 Jul 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of node-deep-extend are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor node-deep-extend for upcoming vulnerabilities?

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