VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mathjs: vulnerability history, versions and safety

mathjs is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 119 releases, from Dec 2017 to Apr 2026. 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 H3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 16 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mathjs vulnerabilities

Vulert verdict on mathjs 15.2.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 15.2.0 — unaffected i
  • Vulnerabilities on record 5 over 8 years · 2 in the last year i
  • Latest disclosure 16 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 591 packages i
  • Stars 15,087 i
  • OpenSSF scorecard 4/10 i
  • Last release 6 months ago i
  • Licence Apache-2.0 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 mathjs, 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
15.2.0 07 Apr 2026 none Apache-2.0 — Details →
15.1.1 10 Feb 2026 H2 Apache-2.0 Yes Details →
15.1.0 05 Nov 2025 H2 Apache-2.0 Yes Details →
15.0.0 10 Oct 2025 H2 Apache-2.0 Yes Details →
14.9.1 10 Oct 2025 H2 Apache-2.0 Yes Details →
14.9.0 10 Oct 2025 H2 Apache-2.0 Yes Details →
14.8.2 03 Oct 2025 H2 Apache-2.0 Yes Details →
14.8.1 26 Sep 2025 H2 Apache-2.0 Yes Details →
14.8.0 24 Sep 2025 H2 Apache-2.0 Yes Details →
14.7.0 05 Sep 2025 H2 Apache-2.0 Yes Details →
14.6.0 25 Jul 2025 H2 Apache-2.0 Yes Details →
14.5.3 02 Jul 2025 H2 Apache-2.0 Yes Details →
14.5.2 30 May 2025 H2 Apache-2.0 Yes Details →
14.5.1 28 May 2025 H2 Apache-2.0 Yes Details →
14.5.0 21 May 2025 H2 Apache-2.0 Yes Details →
14.4.0 28 Mar 2025 H2 Apache-2.0 Yes Details →
14.3.1 06 Mar 2025 H2 Apache-2.0 Yes Details →
14.3.0 28 Feb 2025 H2 Apache-2.0 Yes Details →
14.2.1 05 Feb 2025 H2 Apache-2.0 Yes Details →
14.2.0 30 Jan 2025 H2 Apache-2.0 Yes Details →
14.1.0 24 Jan 2025 H2 Apache-2.0 Yes Details →
14.0.1 11 Dec 2024 H2 Apache-2.0 Yes Details →
14.0.0 20 Nov 2024 H2 Apache-2.0 Yes Details →
13.2.3 20 Nov 2024 H2 Apache-2.0 Yes Details →
13.2.2 13 Nov 2024 H2 Apache-2.0 Yes Details →
13.2.1 06 Nov 2024 H2 Apache-2.0 Yes Details →
13.2.0 02 Oct 2024 H2 Apache-2.0 Yes Details →
13.1.1 27 Aug 2024 H2 Apache-2.0 Yes Details →
13.1.0 26 Aug 2024 H1 Apache-2.0 Yes Details →
13.0.3 19 Jul 2024 H1 Apache-2.0 Yes Details →
13.0.2 04 Jul 2024 H1 Apache-2.0 Yes Details →
13.0.1 28 Jun 2024 H1 Apache-2.0 Yes Details →
13.0.0 31 May 2024 H1 Apache-2.0 Yes Details →
12.4.3 31 May 2024 H1 Apache-2.0 Yes Details →
12.4.2 24 Apr 2024 H1 Apache-2.0 Yes Details →
12.4.1 13 Mar 2024 H1 Apache-2.0 Yes Details →
12.4.0 22 Feb 2024 H1 Apache-2.0 Yes Details →
12.3.2 08 Feb 2024 H1 Apache-2.0 Yes Details →
12.3.1 01 Feb 2024 H1 Apache-2.0 Yes Details →
12.3.0 12 Jan 2024 H1 Apache-2.0 Yes Details →
12.2.1 20 Dec 2023 H1 Apache-2.0 Yes Details →
12.2.0 08 Dec 2023 H1 Apache-2.0 Yes Details →
12.1.0 17 Nov 2023 H1 Apache-2.0 Yes Details →
12.0.0 26 Oct 2023 H1 Apache-2.0 Yes Details →
11.12.0 26 Oct 2023 H1 Apache-2.0 Yes Details →
11.11.2 11 Oct 2023 H1 Apache-2.0 Yes Details →
11.11.1 20 Sep 2023 H1 Apache-2.0 Yes Details →
11.11.0 05 Sep 2023 H1 Apache-2.0 Yes Details →
11.10.1 31 Aug 2023 H1 Apache-2.0 Yes Details →
11.10.0 23 Aug 2023 H1 Apache-2.0 Yes Details →
11.9.1 24 Jul 2023 H1 Apache-2.0 Yes Details →
11.9.0 19 Jul 2023 H1 Apache-2.0 Yes Details →
11.8.2 20 Jun 2023 H1 Apache-2.0 Yes Details →
11.8.1 13 Jun 2023 H1 Apache-2.0 Yes Details →
11.8.0 03 Apr 2023 H1 Apache-2.0 Yes Details →
11.7.0 15 Mar 2023 H1 Apache-2.0 Yes Details →
11.6.0 24 Feb 2023 H1 Apache-2.0 Yes Details →
11.5.1 31 Jan 2023 H1 Apache-2.0 Yes Details →
11.5.0 05 Dec 2022 H1 Apache-2.0 Yes Details →
11.4.0 18 Nov 2022 H1 Apache-2.0 Yes Details →
11.3.3 07 Nov 2022 H1 Apache-2.0 Yes Details →
11.3.2 25 Oct 2022 H1 Apache-2.0 Yes Details →
11.3.1 19 Oct 2022 H1 Apache-2.0 Yes Details →
11.3.0 11 Oct 2022 H1 Apache-2.0 Yes Details →
11.2.1 13 Sep 2022 H1 Apache-2.0 Yes Details →
11.2.0 12 Sep 2022 H1 Apache-2.0 Yes Details →
11.1.0 23 Aug 2022 H1 Apache-2.0 Yes Details →
11.0.1 25 Jul 2022 H1 Apache-2.0 Yes Details →
11.0.0 23 Jul 2022 H1 Apache-2.0 Yes Details →
10.6.4 28 Jun 2022 H1 Apache-2.0 Yes Details →
10.6.3 24 Jun 2022 H1 Apache-2.0 Yes Details →
10.6.2 24 Jun 2022 H1 Apache-2.0 Yes Details →
10.6.1 31 May 2022 H1 Apache-2.0 Yes Details →
10.6.0 24 May 2022 H1 Apache-2.0 Yes Details →
10.5.3 11 May 2022 H1 Apache-2.0 Yes Details →
10.5.2 09 May 2022 H1 Apache-2.0 Yes Details →
10.5.1 02 May 2022 H1 Apache-2.0 Yes Details →
10.5.0 19 Apr 2022 H1 Apache-2.0 Yes Details →
10.4.3 08 Apr 2022 H1 Apache-2.0 Yes Details →
10.4.2 29 Mar 2022 H1 Apache-2.0 Yes Details →
10.4.1 23 Mar 2022 H1 Apache-2.0 Yes Details →
10.4.0 07 Mar 2022 H1 Apache-2.0 Yes Details →
10.3.0 02 Mar 2022 H1 Apache-2.0 Yes Details →
10.2.0 01 Mar 2022 H1 Apache-2.0 Yes Details →
10.1.1 02 Feb 2022 H1 Apache-2.0 Yes Details →
10.1.0 15 Jan 2022 H1 Apache-2.0 Yes Details →
10.0.2 29 Dec 2021 H1 Apache-2.0 Yes Details →
10.0.1 22 Dec 2021 H1 Apache-2.0 Yes Details →
10.0.0 03 Nov 2021 H1 Apache-2.0 Yes Details →
9.5.2 03 Nov 2021 H1 Apache-2.0 Yes Details →
9.5.1 13 Oct 2021 H1 Apache-2.0 Yes Details →
9.5.0 22 Sep 2021 H1 Apache-2.0 Yes Details →
9.4.5 15 Sep 2021 H1 Apache-2.0 Yes Details →
9.4.4 07 Jul 2021 H1 Apache-2.0 Yes Details →
9.4.3 23 Jun 2021 H1 Apache-2.0 Yes Details →
9.4.2 05 Jun 2021 H1 Apache-2.0 Yes Details →
9.4.1 24 May 2021 H1 Apache-2.0 Yes Details →
9.4.0 16 May 2021 H1 Apache-2.0 Yes Details →
9.3.2 12 Apr 2021 H1 Apache-2.0 Yes Details →
9.3.1 10 Apr 2021 H1 Apache-2.0 Yes Details →
9.3.0 10 Mar 2021 H1 — Yes Details →
9.2.0 03 Feb 2021 H1 — Yes Details →
9.1.0 27 Jan 2021 H1 — Yes Details →
9.0.0 16 Jan 2021 H1 — Yes Details →
8.1.1 30 Dec 2020 H1 — Yes Details →
8.1.0 04 Dec 2020 H1 — Yes Details →
8.0.1 09 Nov 2020 H1 — Yes Details →
8.0.0 06 Nov 2020 H1 — Yes Details →
8.0.0-beta.1 06 Nov 2020 H1 — Yes Details →
7.6.0 02 Nov 2020 H1 — Yes Details →
8.0.0-beta.0 18 Oct 2020 H1 — Yes Details →
7.5.1 10 Oct 2020 H1 — Yes Details →
7.5.0 07 Oct 2020 H2 — Yes Details →
7.4.0 07 Oct 2020 H2 — Yes Details →
7.3.0 26 Sep 2020 H2 — Yes Details →
7.2.0 24 Aug 2020 H2 — Yes Details →
7.1.0 13 Jul 2020 H2 — Yes Details →
7.0.2 24 Jun 2020 H2 — Yes Details →
7.0.1 30 May 2020 H2 — Yes Details →
7.0.0 07 May 2020 H2 — Yes Details →

The newest 120 of 306 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2021 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for mathjs

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2017-1001003: Arbitrary Code Execution in mathjs 9.8 critical 3.17.0 18 Dec 2017
CVE-2017-1001002: Arbitrary Code Execution in mathjs 9.8 critical 3.17.0 18 Dec 2017
High Severity Vulnerability in mathjs: Improperly Controlled Modification of Dynamically-Determined Object Attributes 8.8 high 15.2.0 10 Apr 2026
CVE-2026-40897: mathjs Arbitrary JavaScript Execution via Expression Parser 8.8 high 15.2.0 16 Apr 2026
CVE-2020-7743: Prototype Pollution in mathjs 7.3 high 7.5.1 10 May 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 mathjs

Is mathjs safe to use?

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

Vulert scores mathjs 75/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 mathjs affected?

No. 15.2.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 mathjs should I use?

15.2.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 mathjs have?

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

2 vulnerabilities were recorded for mathjs in the last 12 months, and the oldest entry in this database dates to 18 Dec 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 mathjs 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 mathjs for upcoming vulnerabilities?

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