VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dotenv: vulnerability history, versions and safety

dotenv is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

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 dotenv vulnerabilities

Vulert verdict on dotenv 18.0.9 i

Updated on 23 Oct 2026

Good news: 18.0.9, the version you would install today, has no known vulnerabilities.

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 18.0.9 or newer. This can change: a vulnerability disclosed tomorrow can affect 18.0.9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 18.0.9 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 20,547 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for dotenv, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
18.0.9 22 Oct 2026 none BSD-2-Clause — Details →
18.0.8 14 Oct 2026 none BSD-2-Clause — Details →
18.0.7 09 Oct 2026 none BSD-2-Clause — Details →
18.0.6 06 Oct 2026 none BSD-2-Clause — Details →
18.0.5 30 Sep 2026 none BSD-2-Clause — Details →
18.0.4 25 Sep 2026 none BSD-2-Clause — Details →
18.0.3 22 Sep 2026 none BSD-2-Clause — Details →
18.0.2 21 Sep 2026 none BSD-2-Clause — Details →
18.0.1 18 Sep 2026 none BSD-2-Clause — Details →
18.0.0 17 Sep 2026 none BSD-2-Clause — Details →
17.4.2 12 Apr 2026 none BSD-2-Clause — Details →
17.4.1 05 Apr 2026 none BSD-2-Clause — Details →
17.4.0 01 Apr 2026 none BSD-2-Clause — Details →
17.3.1 12 Feb 2026 none BSD-2-Clause — Details →
17.3.0 12 Feb 2026 none BSD-2-Clause — Details →
17.2.4 05 Feb 2026 none BSD-2-Clause — Details →
17.2.3 29 Sep 2025 none BSD-2-Clause — Details →
17.2.2 02 Sep 2025 none BSD-2-Clause — Details →
17.2.1 24 Jul 2025 none BSD-2-Clause — Details →
17.2.0 09 Jul 2025 none BSD-2-Clause — Details →
17.1.0 08 Jul 2025 none BSD-2-Clause — Details →
17.0.1 01 Jul 2025 none BSD-2-Clause — Details →
17.0.0 27 Jun 2025 none BSD-2-Clause — Details →
16.6.1 27 Jun 2025 none BSD-2-Clause — Details →
16.6.0 26 Jun 2025 none BSD-2-Clause — Details →
16.5.0 10 Apr 2025 none BSD-2-Clause — Details →
16.4.7 03 Dec 2024 none BSD-2-Clause — Details →
16.4.6 03 Dec 2024 none BSD-2-Clause — Details →
16.4.5 20 Feb 2024 none BSD-2-Clause — Details →
16.4.4 13 Feb 2024 none BSD-2-Clause — Details →
16.4.3 12 Feb 2024 none BSD-2-Clause — Details →
16.4.2 10 Feb 2024 none BSD-2-Clause — Details →
16.4.1 24 Jan 2024 none BSD-2-Clause — Details →
16.4.0 23 Jan 2024 none BSD-2-Clause — Details →
16.3.2 19 Jan 2024 none BSD-2-Clause — Details →
16.3.1 17 Jun 2023 none BSD-2-Clause — Details →
16.3.0 16 Jun 2023 none BSD-2-Clause — Details →
16.2.0 16 Jun 2023 none BSD-2-Clause — Details →
16.1.4 04 Jun 2023 none BSD-2-Clause — Details →
16.1.3 31 May 2023 none BSD-2-Clause — Details →
16.1.2 31 May 2023 none BSD-2-Clause — Details →
16.1.1 31 May 2023 none BSD-2-Clause — Details →
16.1.0 30 May 2023 none BSD-2-Clause — Details →
16.1.0-rc2 21 May 2023 none BSD-2-Clause — Details →
16.1.0-rc1 07 Apr 2023 none BSD-2-Clause — Details →
16.0.3 29 Sep 2022 none BSD-2-Clause — Details →
16.0.2 30 Aug 2022 none BSD-2-Clause — Details →
16.0.1 10 May 2022 none BSD-2-Clause — Details →
16.0.0 02 Feb 2022 none BSD-2-Clause — Details →
15.0.1 02 Feb 2022 none BSD-2-Clause — Details →
15.0.0 31 Jan 2022 none BSD-2-Clause — Details →
14.3.2 25 Jan 2022 none BSD-2-Clause — Details →
14.3.1 25 Jan 2022 none BSD-2-Clause — Details →
14.3.0 24 Jan 2022 none BSD-2-Clause — Details →
14.2.0 17 Jan 2022 none BSD-2-Clause — Details →
14.1.1 17 Jan 2022 none BSD-2-Clause — Details →
14.1.0 17 Jan 2022 none BSD-2-Clause — Details →
14.0.1 17 Jan 2022 none BSD-2-Clause — Details →
14.0.0 17 Jan 2022 none BSD-2-Clause — Details →
13.0.1 16 Jan 2022 none BSD-2-Clause — Details →
13.0.0 16 Jan 2022 none BSD-2-Clause — Details →
12.0.4 16 Jan 2022 none BSD-2-Clause — Details →
12.0.3 15 Jan 2022 none BSD-2-Clause — Details →
12.0.2 15 Jan 2022 none BSD-2-Clause — Details →
12.0.1 15 Jan 2022 none BSD-2-Clause — Details →
12.0.0 14 Jan 2022 none BSD-2-Clause — Details →
11.0.0 11 Jan 2022 none BSD-2-Clause — Details →
10.0.0 21 May 2021 none BSD-2-Clause — Details →
9.0.2 10 May 2021 none BSD-2-Clause — Details →
9.0.1 09 May 2021 none BSD-2-Clause — Details →
9.0.0 05 May 2021 none BSD-2-Clause — Details →
8.6.0 05 May 2021 none BSD-2-Clause — Details →
8.5.1 05 May 2021 none BSD-2-Clause — Details →
8.5.0 05 May 2021 none BSD-2-Clause — Details →
8.4.0 05 May 2021 none BSD-2-Clause — Details →
8.3.0 05 May 2021 none BSD-2-Clause — Details →
8.2.0 16 Oct 2019 none BSD-2-Clause — Details →
8.1.0 18 Aug 2019 none BSD-2-Clause — Details →
8.0.0 02 May 2019 none BSD-2-Clause — Details →
7.0.0 13 Mar 2019 none BSD-2-Clause — Details →
6.2.0 05 Dec 2018 none BSD-2-Clause — Details →
6.2.0-0 04 Dec 2018 none BSD-2-Clause — Details →
6.2.0-rc1 01 Nov 2018 none BSD-2-Clause — Details →
6.1.0 08 Oct 2018 none BSD-2-Clause — Details →
6.0.0 02 Jun 2018 none BSD-2-Clause — Details →
5.0.1 26 Feb 2018 none BSD-2-Clause — Details →
5.0.0 29 Jan 2018 none BSD-2-Clause — Details →
4.0.0 07 Jan 2017 none BSD-2-Clause — Details →
3.0.0 07 Jan 2017 none BSD-2-Clause — Details →
2.0.0 21 Jan 2016 none BSD-2-Clause — Details →
1.2.0 21 Jun 2015 none BSD-2-Clause — Details →
1.1.0 01 Apr 2015 none non-standard — Details →
1.0.0 14 Mar 2015 none non-standard — Details →
0.5.1 28 Jan 2015 none non-standard — Details →
0.5.0 27 Jan 2015 none non-standard — Details →
0.4.0 28 Jun 2014 none non-standard — Details →
0.3.0 24 Jun 2014 none non-standard — Details →
0.2.8 17 Apr 2014 none non-standard — Details →
0.2.7 27 Mar 2014 none non-standard — Details →
0.2.6 27 Mar 2014 none non-standard — Details →
0.2.5 28 Feb 2014 none — — Details →
0.2.4 08 Feb 2014 none — — Details →
0.2.3 19 Nov 2013 none — — Details →
0.2.2 18 Nov 2013 none — — Details →
0.2.1 15 Nov 2013 none — — Details →
0.2.0 03 Nov 2013 none — — Details →
0.1.2 03 Nov 2013 none — — Details →
0.1.1 03 Nov 2013 none — — Details →
0.1.0 03 Nov 2013 none — — Details →
0.0.5 31 Oct 2013 none — — Details →
0.0.4 31 Oct 2013 none — — Details →
0.0.3 23 Aug 2013 none — — Details →
0.0.2 10 Jul 2013 none — — Details →
0.0.1 05 Jul 2013 none — — Details →

All 114 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for dotenv

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 dotenv

Is dotenv safe to use?

Vulert has no vulnerabilities on record for dotenv in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is dotenv's Vulert package health score?

Vulert scores dotenv 89/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of dotenv affected?

No. 18.0.9, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does dotenv have?

0 vulnerabilities are recorded for dotenv in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dotenv vulnerabilities disclosed?

0 vulnerabilities were recorded for dotenv in the last 12 months. 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 dotenv 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 dotenv for upcoming vulnerabilities?

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