VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

grunt: vulnerability history, versions and safety

grunt is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 68 releases, from May 2021 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 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 grunt vulnerabilities

Vulert verdict on grunt 1.6.3 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.6.3 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 11 May 2022 i
  • Highest CVSS 7.1 i
  • With no published fix 0 i
  • Depended on by 1,108 packages i
  • Stars 12,232 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence MIT 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 grunt, 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.6.3 28 Jul 2026 none MIT — Details →
1.6.2 14 Apr 2026 none MIT — Details →
1.6.1 31 Jan 2023 none MIT — Details →
1.6.0 29 Jan 2023 none MIT — Details →
1.5.3 10 May 2022 none MIT — Details →
1.5.2 12 Apr 2022 H1 MIT Yes Details →
1.5.1 11 Apr 2022 H1 M1 MIT Yes Details →
1.5.0 11 Apr 2022 H1 M1 MIT Yes Details →
1.4.1 24 May 2021 H1 M1 MIT Yes Details →
1.4.0 22 Apr 2021 H1 M1 MIT Yes Details →
1.3.0 18 Aug 2020 H1 M1 MIT Yes Details →
1.2.1 07 Jul 2020 H2 M1 MIT Yes Details →
1.2.0 03 Jul 2020 H2 M1 MIT Yes Details →
1.1.0 17 Mar 2020 H2 M1 MIT Yes Details →
1.0.4 22 Mar 2019 H2 M1 MIT Yes Details →
1.0.3 04 Jun 2018 H2 M1 MIT Yes Details →
1.0.2 07 Feb 2018 H2 M1 MIT Yes Details →
1.0.1 05 Apr 2016 H2 M1 MIT Yes Details →
1.0.0 04 Apr 2016 H2 M1 MIT Yes Details →
1.0.0-rc1 11 Feb 2016 H2 M1 MIT Yes Details →
0.4.5 12 May 2014 H2 M1 MIT Yes Details →
0.4.4 12 Mar 2014 H2 M1 MIT Yes Details →
0.4.3 07 Mar 2014 H2 M1 MIT Yes Details →
0.4.2 21 Nov 2013 H2 M1 MIT Yes Details →
0.4.1 13 Mar 2013 H2 M1 MIT Yes Details →
0.4.0 18 Feb 2013 H2 M1 MIT Yes Details →
0.4.0-rc8 14 Feb 2013 H2 M1 MIT Yes Details →
0.4.0-rc7 21 Jan 2013 H2 M1 MIT Yes Details →
0.4.0-rc6 18 Jan 2013 H2 M1 MIT Yes Details →
0.4.0-rc5 09 Jan 2013 H2 M1 MIT Yes Details →
0.4.0-rc4 17 Dec 2012 H2 M1 MIT Yes Details →
0.4.0-rc3 12 Dec 2012 H2 M1 MIT Yes Details →
0.4.0-rc2 10 Dec 2012 H2 M1 MIT Yes Details →
0.4.0-rc1 07 Dec 2012 H2 M1 MIT Yes Details →
0.4.0-a 05 Dec 2012 H2 M1 MIT Yes Details →
0.3.17 15 Oct 2012 H2 M1 MIT Yes Details →
0.3.16 02 Oct 2012 H2 M1 MIT Yes Details →
0.3.15 04 Sep 2012 H2 M1 MIT Yes Details →
0.3.14 29 Aug 2012 H2 M1 MIT Yes Details →
0.3.13 27 Aug 2012 H2 M1 MIT Yes Details →
0.3.13-a 27 Aug 2012 H2 M1 MIT Yes Details →
0.3.12 30 Jul 2012 H2 M1 MIT Yes Details →
0.3.11 29 Jun 2012 H2 M1 MIT Yes Details →
0.3.10 25 Jun 2012 H2 M1 MIT Yes Details →
0.3.9 18 Apr 2012 H2 M1 MIT Yes Details →
0.3.8 06 Apr 2012 H2 M1 MIT Yes Details →
0.3.7 01 Apr 2012 H2 M1 MIT Yes Details →
0.3.6 29 Mar 2012 H2 M1 MIT Yes Details →
0.3.5 28 Mar 2012 H2 M1 MIT Yes Details →
0.3.4 27 Mar 2012 H2 M1 MIT Yes Details →
0.3.3 27 Mar 2012 H2 M1 MIT Yes Details →
0.3.2 26 Mar 2012 H2 M1 MIT Yes Details →
0.3.1 25 Mar 2012 H2 M1 MIT Yes Details →
0.3.0 23 Mar 2012 H2 M1 MIT Yes Details →
0.2.15 07 Feb 2012 H2 M1 MIT Yes Details →
0.2.14 03 Feb 2012 H2 M1 MIT Yes Details →
0.2.13 02 Feb 2012 H2 M1 MIT Yes Details →
0.2.12 01 Feb 2012 H2 M1 MIT Yes Details →
0.2.11 01 Feb 2012 H2 M1 MIT Yes Details →
0.2.10 01 Feb 2012 H2 M1 MIT Yes Details →
0.2.9 31 Jan 2012 H2 M1 MIT Yes Details →
0.2.8 30 Jan 2012 H2 M1 MIT Yes Details →
0.2.7 30 Jan 2012 H2 M1 MIT Yes Details →
0.2.6 30 Jan 2012 H2 M1 MIT Yes Details →
0.2.5 29 Jan 2012 H2 M1 MIT Yes Details →
0.2.4 23 Jan 2012 H2 M1 MIT Yes Details →
0.2.3 23 Jan 2012 H2 M1 MIT Yes Details →
0.2.2 23 Jan 2012 H2 M1 MIT Yes Details →
0.2.1 23 Jan 2012 H2 M1 MIT Yes Details →
0.2.0 22 Jan 2012 H2 M1 MIT Yes Details →
0.1.2 19 Jan 2012 H2 M1 MIT Yes Details →
0.1.1 19 Jan 2012 H2 M1 MIT Yes Details →
0.1.0 12 Jan 2012 H2 M1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for grunt

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7729: Arbitrary Code Execution in grunt 7.1 high 1.3.0 06 May 2021
CVE-2022-1537: Race Condition in Grunt 7.0 high 1.5.3 11 May 2022
CVE-2022-0436: Path Traversal in Grunt 5.5 medium 1.5.2 13 Apr 2022

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 grunt

Is grunt safe to use?

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

Vulert scores grunt 83/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 grunt affected?

No. 1.6.3, 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 grunt should I use?

1.6.3 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 grunt have?

3 vulnerabilities are recorded for grunt in the npm ecosystem: 0 critical, 2 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 grunt vulnerabilities disclosed?

0 vulnerabilities were recorded for grunt in the last 12 months, and the oldest entry in this database dates to 06 May 2021. 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 grunt 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 grunt for upcoming vulnerabilities?

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