VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pug: vulnerability history, versions and safety

pug is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 35 releases, first recorded in Mar 2021. 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 pug vulnerabilities

Vulert verdict on pug 3.0.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.0.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Mar 2021 i
  • Highest CVSS 6.8 i
  • With no published fix 0 i
  • Depended on by 9,710 packages i
  • Stars 21,826 i
  • OpenSSF scorecard 2/10 i
  • Last release 7 months ago i
  • Licence MIT i
  • Similar names pg 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 pug, 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
3.0.4 13 Mar 2026 none MIT — Details →
3.0.4-canary-8 13 Mar 2026 none MIT — Details →
3.0.3 24 May 2024 none MIT — Details →
3.0.3-canary-14 24 May 2024 none MIT — Details →
3.0.2 28 Feb 2021 none MIT — Details →
3.0.2-canary-10 28 Feb 2021 none MIT — Details →
3.0.1 28 Feb 2021 none MIT — Details →
3.0.1-canary-5 28 Feb 2021 M1 MIT Yes Details →
3.0.0 25 May 2020 M1 MIT Yes Details →
3.0.0-canary-2 25 May 2020 M1 MIT Yes Details →
3.0.0-canary-1 24 May 2020 M1 MIT Yes Details →
2.0.4 18 Jun 2019 M1 MIT Yes Details →
2.0.3 21 Mar 2018 M1 MIT Yes Details →
2.0.2 20 Mar 2018 M1 MIT Yes Details →
2.0.1 08 Mar 2018 M1 MIT Yes Details →
2.0.0 06 Mar 2018 M1 MIT Yes Details →
2.0.0-rc.4 06 Sep 2017 M1 MIT Yes Details →
2.0.0-rc.3 01 Aug 2017 M1 MIT Yes Details →
2.0.0-rc.2 02 Jun 2017 M1 MIT Yes Details →
2.0.0-rc.1 01 May 2017 M1 MIT Yes Details →
2.0.0-beta.12 18 Apr 2017 M1 MIT Yes Details →
2.0.0-beta11 04 Feb 2017 M1 MIT Yes Details →
2.0.0-beta10 29 Jan 2017 M1 MIT Yes Details →
2.0.0-beta9 25 Jan 2017 M1 MIT Yes Details →
2.0.0-beta8 25 Jan 2017 M1 MIT Yes Details →
2.0.0-beta7 24 Jan 2017 M1 MIT Yes Details →
2.0.0-beta6 26 Aug 2016 M1 MIT Yes Details →
2.0.0-beta5 10 Aug 2016 M1 MIT Yes Details →
2.0.0-beta4 18 Jul 2016 M1 MIT Yes Details →
2.0.0-beta3 11 Jun 2016 M1 MIT Yes Details →
2.0.0-beta2 03 Jun 2016 M1 MIT Yes Details →
2.0.0-beta1 03 Jun 2016 M1 MIT Yes Details →
2.0.0-alpha8 22 May 2016 M1 MIT Yes Details →
2.0.0-alpha7 09 May 2016 M1 MIT Yes Details →
2.0.0-alpha6 18 Apr 2016 M1 MIT Yes Details →
2.0.0-alpha5 18 Apr 2016 M1 MIT Yes Details →
2.0.0-alpha4 17 Apr 2016 M1 MIT Yes Details →
2.0.0-alpha3 07 Apr 2016 M1 MIT Yes Details →
2.0.0-alpha2 07 Apr 2016 M1 MIT Yes Details →
2.0.0-alpha1 15 Mar 2016 M1 MIT Yes Details →
0.1.0 12 Dec 2015 M1 MIT Yes Details →
0.0.0 22 Aug 2013 M1 MIT Yes Details →

All 42 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

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 pug

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-21353: Remote Code Execution in pug 6.8 medium 3.0.1 03 Mar 2021

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 pug

Is pug safe to use?

Vulert records 1 vulnerabilities for pug 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 pug's Vulert package health score?

Vulert scores pug 82/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 pug affected?

No. 3.0.4, 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 pug should I use?

3.0.4 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 pug have?

1 vulnerability is recorded for pug 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 pug vulnerabilities disclosed?

0 vulnerabilities were recorded for pug in the last 12 months, and the oldest entry in this database dates to 03 Mar 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 pug 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 pug for upcoming vulnerabilities?

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