VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ejs: vulnerability history, versions and safety

ejs is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 74 releases, from Nov 2017 to Apr 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C2 H1 M2
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 ejs vulnerabilities

Vulert verdict on ejs 7.0.2 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 7.0.2 — unaffected i
  • Vulnerabilities on record 5 over 6 years · 0 in the last year i
  • Latest disclosure 28 Apr 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 702 packages i
  • Stars 8,123 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 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 ejs, 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
7.0.2 18 Oct 2026 none Apache-2.0 — Details →
7.0.1 04 Oct 2026 none Apache-2.0 — Details →
6.0.1 26 May 2026 none Apache-2.0 — Details →
5.0.2 11 Apr 2026 none Apache-2.0 — Details →
5.0.1 05 Mar 2026 none Apache-2.0 — Details →
4.0.1 14 Jan 2026 none Apache-2.0 — Details →
3.1.10 12 Apr 2024 none Apache-2.0 — Details →
3.1.9 12 Mar 2023 M1 Apache-2.0 Yes Details →
3.1.8 11 May 2022 M1 Apache-2.0 Yes Details →
3.1.7 20 Apr 2022 M1 Apache-2.0 Yes Details →
3.1.6 06 Feb 2021 C1 M1 Apache-2.0 Yes Details →
3.1.5 17 Aug 2020 C1 M1 Apache-2.0 Yes Details →
3.1.4 17 Aug 2020 C1 M1 Apache-2.0 Yes Details →
3.1.3 17 May 2020 C1 M1 Apache-2.0 Yes Details →
3.1.2 24 Apr 2020 C1 M1 Apache-2.0 Yes Details →
3.0.2 29 Mar 2020 C1 M1 Apache-2.0 Yes Details →
3.0.1 24 Nov 2019 C1 M1 Apache-2.0 Yes Details →
2.7.4 19 Nov 2019 C1 M1 Apache-2.0 Yes Details →
2.7.3 19 Nov 2019 C1 M1 Apache-2.0 Yes Details →
2.7.2 13 Nov 2019 C1 M1 Apache-2.0 Yes Details →
2.7.1 02 Sep 2019 C1 M1 Apache-2.0 Yes Details →
2.6.2 15 Jun 2019 C1 M1 Apache-2.0 Yes Details →
2.6.1 05 May 2018 C1 M1 Apache-2.0 Yes Details →
2.5.9 19 Apr 2018 C1 M1 Apache-2.0 Yes Details →
2.5.8 26 Mar 2018 C1 M1 Apache-2.0 Yes Details →
2.5.7 30 Jul 2017 C1 M1 Apache-2.0 Yes Details →
2.5.6 16 Feb 2017 C1 M1 Apache-2.0 Yes Details →
2.5.5 06 Dec 2016 C1 M1 Apache-2.0 Yes Details →
2.5.4 05 Dec 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.5.3 28 Nov 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.5.2 07 Sep 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.5.1 25 Jul 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.4.2 24 May 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.4.1 24 Jan 2016 C2 H1 M2 Apache-2.0 Yes Details →
2.3.4 07 Sep 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.3.3 11 Jul 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.3.2 29 Jun 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.3.1 23 Feb 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.2.4 01 Feb 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.2.3 23 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.2.2 21 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.2.1 20 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.1.4 12 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.1.3 12 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.1.2 11 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.1.1 11 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.8 06 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.7 05 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.6 05 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.5 04 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.4 04 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.3 04 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
2.0.2 04 Jan 2015 C2 H1 M2 Apache-2.0 Yes Details →
1.0.0 24 Mar 2014 C2 H1 M2 Apache-2.0 Yes Details →
0.8.8 24 Mar 2014 C2 H1 M2 Apache-2.0 Yes Details →
0.8.6 21 Mar 2014 C2 H1 M2 Apache-2.0 Yes Details →
0.8.5 22 Nov 2013 C2 H1 M2 Apache-2.0 Yes Details →
0.8.4 08 May 2013 C2 H1 M2 Apache-2.0 Yes Details →
0.8.3 13 Sep 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.8.2 16 Aug 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.8.1 11 Aug 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.8.0 25 Jul 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.7.2 22 Jun 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.7.1 26 Mar 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.7.0 25 Mar 2012 C2 H1 M2 Apache-2.0 Yes Details →
0.6.1 10 Dec 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.6.0 09 Dec 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.5.0 20 Nov 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.4.3 20 Jun 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.4.2 11 May 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.4.1 21 Apr 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.4.0 21 Apr 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.3.1 24 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.0.1 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.0.2 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.0.3 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.0.4 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.1.0 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.2.0 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.2.1 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →
0.3.0 14 Feb 2011 C2 H1 M2 Apache-2.0 Yes Details →

All 81 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 2
  • 2018 1
  • 2022 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for ejs

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000228: Remote Code Execution in ejs 9.8 critical 2.5.5 30 Nov 2017
CVE-2022-29078: ejs template injection vulnerability 9.8 critical 3.1.7 26 Apr 2022
ejs vulnerable to DoS due to weak input validation 7.5 high 2.5.5 05 Mar 2018
CVE-2017-1000188: Cross-site Scripting Vulnerability in ejs 6.1 medium 2.5.5 30 Nov 2017
Vulnerability in ejs Package: Lack of Pollution Protection 4.0 medium 3.1.10 28 Apr 2024

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 ejs

Is ejs safe to use?

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

Vulert scores ejs 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 ejs affected?

No. 7.0.2, 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 ejs have?

5 vulnerabilities are recorded for ejs in the npm ecosystem: 2 critical, 1 high, 2 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 ejs vulnerabilities disclosed?

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

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