VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

expr-eval: vulnerability history, versions and safety

expr-eval is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 17 releases, from Nov 2025 to Jun 2026. 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 C1 H2
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 23 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all expr-eval vulnerabilities

Vulert verdict on expr-eval 2.0.2 i

Updated on 23 Oct 2026

Careful: 2.0.2 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 51/100
  • Security Unfixed issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.0.2 — affected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 23 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 3 i
  • Depended on by 2,299 packages i
  • Stars 1,354 i
  • OpenSSF scorecard 1/10 i
  • Last release 84 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 expr-eval, 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.0.2 28 Sep 2019 C1 H2 MIT No Details →
2.0.1 10 Sep 2019 C1 H2 MIT No Details →
2.0.0 08 Sep 2019 C1 H2 MIT No Details →
1.2.3 10 Jul 2019 C1 H2 MIT No Details →
1.2.2 03 Jul 2018 C1 H2 MIT No Details →
1.2.1 21 Dec 2017 C1 H2 MIT No Details →
1.2.0 25 Sep 2017 C1 H2 MIT No Details →
1.1.1 06 Sep 2017 C1 H2 MIT No Details →
1.1.0 30 Aug 2017 C1 H2 MIT No Details →
1.0.1 10 Jun 2017 C1 H2 MIT No Details →
1.0.0 02 Jan 2017 C1 H2 MIT No Details →
1.0.0-rc.4 29 Dec 2016 C1 H2 MIT No Details →
1.0.0-rc.3 28 Nov 2016 C1 H2 MIT No Details →
0.12.0 13 Oct 2016 C1 H2 MIT No Details →
0.10.1 02 Oct 2016 C1 H2 MIT No Details →
0.10.0 29 Sep 2016 C1 H2 MIT No Details →
0.9.0 14 Sep 2016 C1 H2 MIT No Details →

All 17 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 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for expr-eval

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-12866: expr-eval Package Vulnerable to Code Execution 9.8 critical No fix published 23 Jun 2026
CVE-2025-12735: expr-eval Arbitrary Code Execution Vulnerability 8.6 high No fix published 05 Nov 2025
CVE-2025-13204: expr-eval Package Vulnerable to Prototype Pollution 7.3 high No fix published 14 Nov 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 expr-eval

Is expr-eval safe to use?

Vulert records 3 vulnerabilities for expr-eval in npm: 1 critical, 2 high, 0 medium and 0 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is expr-eval's Vulert package health score?

Vulert scores expr-eval 51/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of expr-eval affected?

Yes. 2.0.2, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does expr-eval have?

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

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

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