VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mammoth: vulnerability history, versions and safety

mammoth is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 61 releases, first recorded in Oct 2025. 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 M1
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 mammoth vulnerabilities

Vulert verdict on mammoth 1.13.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 1.13.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 Oct 2025 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 2,500 packages i
  • Stars 6,324 i
  • OpenSSF scorecard 2/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 mammoth, 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
1.13.0 26 Sep 2026 none BSD-2-Clause — Details →
1.12.3 12 Sep 2026 none BSD-2-Clause — Details →
1.12.2 28 Aug 2026 none BSD-2-Clause — Details →
1.12.1 09 Aug 2026 none BSD-2-Clause — Details →
1.12.0 12 Mar 2026 none BSD-2-Clause — Details →
1.11.0 19 Sep 2025 none BSD-2-Clause — Details →
1.10.0 02 Aug 2025 M1 BSD-2-Clause Yes Details →
1.9.1 28 May 2025 M1 BSD-2-Clause Yes Details →
1.9.0 30 Dec 2024 M1 BSD-2-Clause Yes Details →
1.8.0 16 Jun 2024 M1 BSD-2-Clause Yes Details →
1.7.2 27 Apr 2024 M1 BSD-2-Clause Yes Details →
1.7.1 20 Mar 2024 M1 BSD-2-Clause Yes Details →
1.7.0 18 Feb 2024 M1 BSD-2-Clause Yes Details →
1.6.0 30 May 2023 M1 BSD-2-Clause Yes Details →
1.5.1 31 Aug 2022 M1 BSD-2-Clause Yes Details →
1.5.0 31 Aug 2022 M1 BSD-2-Clause Yes Details →
1.4.21 09 Mar 2022 M1 BSD-2-Clause Yes Details →
1.4.19 19 Oct 2021 M1 BSD-2-Clause Yes Details →
1.4.18 28 Aug 2021 M1 BSD-2-Clause Yes Details →
1.4.17 17 May 2021 M1 BSD-2-Clause Yes Details →
1.4.16 19 Jan 2021 M1 BSD-2-Clause Yes Details →
1.4.15 09 Jan 2021 M1 BSD-2-Clause Yes Details →
1.4.14 05 Nov 2020 M1 BSD-2-Clause Yes Details →
1.4.13 09 Sep 2020 M1 BSD-2-Clause Yes Details →
1.4.12 09 Sep 2020 M1 BSD-2-Clause Yes Details →
1.4.11 15 Aug 2020 M1 BSD-2-Clause Yes Details →
1.4.10 15 Aug 2020 M1 BSD-2-Clause Yes Details →
1.4.9 03 Nov 2019 M1 BSD-2-Clause Yes Details →
1.4.8 17 Mar 2019 M1 BSD-2-Clause Yes Details →
1.4.7 07 Nov 2018 M1 BSD-2-Clause Yes Details →
1.4.6 12 May 2018 M1 BSD-2-Clause Yes Details →
1.4.5 02 Apr 2018 M1 BSD-2-Clause Yes Details →
1.4.4 26 Jan 2018 M1 BSD-2-Clause Yes Details →
1.4.3 04 Nov 2017 M1 BSD-2-Clause Yes Details →
1.4.2 14 Jul 2017 M1 BSD-2-Clause Yes Details →
1.4.1 08 Jun 2017 M1 BSD-2-Clause Yes Details →
1.4.0 30 May 2017 M1 BSD-2-Clause Yes Details →
1.3.6 22 Apr 2017 M1 BSD-2-Clause Yes Details →
1.3.5 13 Apr 2017 M1 BSD-2-Clause Yes Details →
1.3.4 04 Apr 2017 M1 BSD-2-Clause Yes Details →
1.3.3 19 Feb 2017 M1 BSD-2-Clause Yes Details →
1.3.2 23 Jan 2017 M1 BSD-2-Clause Yes Details →
1.3.1 20 Nov 2016 M1 BSD-2-Clause Yes Details →
1.3.0 19 Nov 2016 M1 BSD-2-Clause Yes Details →
1.2.5 04 Oct 2016 M1 BSD-2-Clause Yes Details →
1.2.4 02 Oct 2016 M1 BSD-2-Clause Yes Details →
1.2.3 27 Sep 2016 M1 BSD-2-Clause Yes Details →
1.2.2 16 Sep 2016 M1 BSD-2-Clause Yes Details →
1.2.1 02 Sep 2016 M1 BSD-2-Clause Yes Details →
1.2.0 02 Sep 2016 M1 BSD-2-Clause Yes Details →
1.1.0 07 Jul 2016 M1 BSD-2-Clause Yes Details →
1.0.4 20 Jun 2016 M1 BSD-2-Clause Yes Details →
1.0.3 12 May 2016 M1 BSD-2-Clause Yes Details →
1.0.2 10 May 2016 M1 BSD-2-Clause Yes Details →
1.0.1 02 May 2016 M1 BSD-2-Clause Yes Details →
1.0.0 23 Apr 2016 M1 BSD-2-Clause Yes Details →
0.3.33 23 Mar 2016 M1 BSD-2-Clause Yes Details →
0.3.32 25 Feb 2016 M1 BSD-2-Clause Yes Details →
0.3.31 05 Feb 2016 M1 BSD-2-Clause Yes Details →
0.3.30 13 Jan 2016 M1 BSD-2-Clause Yes Details →
0.3.29 20 Dec 2015 M1 BSD-2-Clause Yes Details →
0.3.28 10 Dec 2015 M1 BSD-2-Clause Yes Details →
0.3.28-pre.1 20 Oct 2015 M1 BSD-2-Clause Yes Details →
0.3.27 14 Oct 2015 M1 BSD-2-Clause Yes Details →
0.3.26 14 Oct 2015 M1 BSD-2-Clause Yes Details →
0.3.25 12 Sep 2015 M1 BSD-2-Clause Yes Details →
0.3.25-pre.1 16 Aug 2015 M1 BSD-2-Clause Yes Details →
0.3.24 04 Aug 2015 none BSD-2-Clause — Details →
0.3.23 03 Jul 2015 none BSD-2-Clause — Details →
0.3.22 17 Jun 2015 none BSD-2-Clause — Details →
0.3.21 14 Jun 2015 none BSD-2-Clause — Details →
0.3.20 24 May 2015 none BSD-2-Clause — Details →
0.3.19 17 May 2015 none BSD-2-Clause — Details →
0.3.18 08 Apr 2015 none BSD-2-Clause — Details →
0.3.17 09 Feb 2015 none BSD-2-Clause — Details →
0.3.16 04 Feb 2015 none BSD-2-Clause — Details →
0.3.15 28 Jan 2015 none BSD-2-Clause — Details →
0.3.14 21 Jan 2015 none BSD-2-Clause — Details →
0.3.13 27 Nov 2014 none BSD-2-Clause — Details →
0.3.12 25 Nov 2014 none BSD-2-Clause — Details →
0.3.11 27 Sep 2014 none BSD-2-Clause — Details →
0.3.10 20 Aug 2014 none BSD-2-Clause — Details →
0.3.9 18 Aug 2014 none BSD-2-Clause — Details →
0.3.8 05 Aug 2014 none BSD-2-Clause — Details →
0.3.7 18 Jul 2014 none BSD-2-Clause — Details →
0.3.6 17 Jul 2014 none BSD-2-Clause — Details →
0.3.5 08 Jul 2014 none BSD-2-Clause — Details →
0.3.4 06 Jul 2014 none BSD-2-Clause — Details →
0.3.3 05 Jul 2014 none BSD-2-Clause — Details →
0.3.2 11 Jun 2014 none BSD-2-Clause — Details →
0.3.1 08 Jun 2014 none BSD-2-Clause — Details →
0.3.0 11 May 2014 none BSD-2-Clause — Details →
0.2.2 10 Apr 2014 none BSD-2-Clause — Details →
0.2.1 24 Mar 2014 none BSD-2-Clause — Details →
0.2.0 23 Mar 2014 none BSD-2-Clause — Details →
0.1.6 23 Dec 2013 none BSD-2-Clause — Details →
0.1.5 26 Nov 2013 none BSD-2-Clause — Details →
0.1.4 24 Oct 2013 none BSD-2-Clause — Details →
0.1.3 11 Jun 2013 none BSD-2-Clause — Details →
0.1.2 06 May 2013 none BSD-2-Clause — Details →
0.1.1 06 May 2013 none — — Details →
0.1.0 06 May 2013 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 mammoth

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-11849: Mammoth Package Vulnerable to Directory Traversal 9.3 medium 1.11.0 17 Oct 2025

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 mammoth

Is mammoth safe to use?

Vulert records 1 vulnerabilities for mammoth in npm: 0 critical, 0 high, 1 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 mammoth's Vulert package health score?

Vulert scores mammoth 78/100, which reads as in good shape. 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 mammoth affected?

No. 1.13.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 mammoth should I use?

1.13.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 mammoth have?

1 vulnerability is recorded for mammoth in the npm ecosystem: 0 critical, 0 high, 1 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 mammoth vulnerabilities disclosed?

0 vulnerabilities were recorded for mammoth in the last 12 months, and the oldest entry in this database dates to 17 Oct 2025. 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 mammoth 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 mammoth for upcoming vulnerabilities?

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