VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

moment: vulnerability history, versions and safety

moment is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 76 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H5 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all moment vulnerabilities

Vulert verdict on moment 2.31.0 i

Updated on 22 Oct 2026

Good news: 2.31.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 8.

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

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

  • Current release 2.31.0 — unaffected i
  • Vulnerabilities on record 8 over 8 years · 1 in the last year i
  • Latest disclosure 29 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 174,208 packages i
  • Stars 47,898 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 moment, 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
2.31.0 15 Sep 2026 none MIT — Details →
2.30.1 27 Dec 2023 M1 MIT Yes Details →
2.30.0 26 Dec 2023 M1 MIT Yes Details →
2.29.4 06 Jul 2022 M1 MIT Yes Details →
2.29.3 17 Apr 2022 H2 M1 MIT Yes Details →
2.29.2 03 Apr 2022 H2 M1 MIT Yes Details →
2.29.1 06 Oct 2020 H4 MIT Yes Details →
2.29.0 22 Sep 2020 H4 MIT Yes Details →
2.28.0 13 Sep 2020 H4 MIT Yes Details →
2.27.0 18 Jun 2020 H4 MIT Yes Details →
2.26.0 20 May 2020 H4 MIT Yes Details →
2.25.3 04 May 2020 H4 MIT Yes Details →
2.25.2 04 May 2020 H4 MIT Yes Details →
2.25.1 01 May 2020 H4 MIT Yes Details →
2.25.0 01 May 2020 H4 MIT Yes Details →
2.24.0 21 Jan 2019 H4 MIT Yes Details →
2.23.0 13 Dec 2018 H4 MIT Yes Details →
2.22.2 01 Jun 2018 H4 MIT Yes Details →
2.22.1 15 Apr 2018 H4 MIT Yes Details →
2.22.0 30 Mar 2018 H4 MIT Yes Details →
2.21.0 02 Mar 2018 H4 MIT Yes Details →
2.20.1 19 Dec 2017 H4 MIT Yes Details →
2.20.0 17 Dec 2017 H4 MIT Yes Details →
2.19.4 11 Dec 2017 H4 MIT Yes Details →
2.19.3 29 Nov 2017 H4 MIT Yes Details →
2.19.2 11 Nov 2017 H5 MIT Yes Details →
2.19.1 11 Oct 2017 H5 MIT Yes Details →
2.19.0 10 Oct 2017 H5 MIT Yes Details →
2.18.1 21 Mar 2017 H5 MIT Yes Details →
2.18.0 18 Mar 2017 H5 MIT Yes Details →
2.17.1 04 Dec 2016 H3 MIT Yes Details →
2.17.0 22 Nov 2016 H3 MIT Yes Details →
2.16.0 10 Nov 2016 H3 MIT Yes Details →
2.15.2 24 Oct 2016 H3 MIT Yes Details →
2.15.1 21 Sep 2016 H3 MIT Yes Details →
2.15.0 12 Sep 2016 H3 MIT Yes Details →
2.14.1 04 Jul 2016 H3 MIT Yes Details →
2.14.0 04 Jul 2016 H3 MIT Yes Details →
2.13.0 18 Apr 2016 H3 MIT Yes Details →
2.12.0 07 Mar 2016 H3 MIT Yes Details →
2.11.2 03 Feb 2016 H3 MIT Yes Details →
2.11.1 09 Jan 2016 H3 M2 MIT Yes Details →
2.11.0 02 Jan 2016 H3 M2 MIT Yes Details →
2.10.6 28 Jul 2015 H3 M2 MIT Yes Details →
2.10.5 26 Jul 2015 H3 M2 MIT Yes Details →
2.10.3 13 May 2015 H3 M2 MIT Yes Details →
2.10.2 09 Apr 2015 H3 M2 MIT Yes Details →
2.9.0 08 Jan 2015 H3 M2 MIT Yes Details →
2.8.4 19 Nov 2014 H3 M2 MIT Yes Details →
2.8.3 05 Sep 2014 H3 M2 MIT Yes Details →
2.8.2 22 Aug 2014 H3 M2 MIT Yes Details →
2.8.1 01 Aug 2014 H3 M2 MIT Yes Details →
2.7.0 12 Jun 2014 H3 M2 MIT Yes Details →
2.6.0 12 Apr 2014 H3 M2 MIT Yes Details →
2.5.1 22 Jan 2014 H3 M2 MIT Yes Details →
2.5.0 23 Dec 2013 H3 M2 MIT Yes Details →
2.4.0 27 Oct 2013 H3 M2 MIT Yes Details →
2.3.1 09 Oct 2013 H3 M2 MIT Yes Details →
2.3.0 07 Oct 2013 H3 M2 MIT Yes Details →
2.2.1 12 Sep 2013 H3 M2 MIT Yes Details →
2.1.0 07 Jul 2013 H3 M2 MIT Yes Details →
2.0.0 08 Feb 2013 H3 M2 MIT Yes Details →
1.7.2 02 Oct 2012 H3 M2 MIT Yes Details →
1.7.1 01 Oct 2012 H3 M2 MIT Yes Details →
1.7.0 25 Jul 2012 H3 M2 MIT Yes Details →
1.6.2 04 May 2012 H3 M2 MIT Yes Details →
1.6.1 26 Apr 2012 H3 M2 MIT Yes Details →
1.6.0 26 Apr 2012 H3 M2 MIT Yes Details →
1.5.1 06 Apr 2012 H3 M2 MIT Yes Details →
1.5.0 19 Mar 2012 H3 M2 MIT Yes Details →
1.4.0 03 Feb 2012 H3 M2 MIT Yes Details →
1.3.0 05 Jan 2012 H3 M2 MIT Yes Details →
1.0.0 06 Dec 2011 H3 M2 MIT Yes Details →
1.0.1 06 Dec 2011 H3 M2 MIT Yes Details →
1.2.0 06 Dec 2011 H3 M2 MIT Yes Details →
1.1.1 11 Nov 2011 H3 M2 MIT Yes Details →
1.1.0 27 Oct 2011 H3 M2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2022 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for moment

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-18214: Regular Expression Denial of Service in moment 7.5 high 2.19.3 05 Mar 2018
CVE-2022-24785: Path Traversal Vulnerability in moment.js 7.5 high 2.29.2 04 Apr 2022
CVE-2022-31129: Moment.js vulnerable to Inefficient Regular Expression Complexity 7.5 high 2.29.4 06 Jul 2022
CVE-2016-4055: Regular Expression Denial of Service in moment 6.5 medium 2.11.2 24 Oct 2017
CVE-2026-17495: Moment.js Path Traversal Vulnerability via Non-String Locale Name 5.9 medium 2.31.0 29 Sep 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524171

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About moment

Is moment safe to use?

Vulert records 8 vulnerabilities for moment in npm: 0 critical, 5 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is moment's Vulert package health score?

Vulert scores moment 85/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 moment affected?

No. 2.31.0, 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.

Which version of moment should I use?

2.31.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does moment have?

8 vulnerabilities are recorded for moment in the npm ecosystem: 0 critical, 5 high, 3 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 moment vulnerabilities disclosed?

1 vulnerability was recorded for moment in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 moment 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 moment for upcoming vulnerabilities?

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