VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

chart.js: vulnerability history, versions and safety

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

Vulert verdict on chart.js 4.6.1 i

Updated on 22 Oct 2026

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

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

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

  • Current release 4.6.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 May 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 67,753 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 chart.js, 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
4.6.1 22 Oct 2026 none MIT — Details →
4.5.1 13 Oct 2025 none MIT — Details →
4.5.0 14 Jun 2025 none MIT — Details →
4.4.9 15 Apr 2025 none MIT — Details →
4.4.8 19 Feb 2025 none MIT — Details →
4.4.7 01 Dec 2024 none MIT — Details →
4.4.6 28 Oct 2024 none MIT — Details →
4.4.5 15 Oct 2024 none MIT — Details →
4.4.4 20 Aug 2024 none MIT — Details →
4.4.3 17 May 2024 none MIT — Details →
4.4.2 28 Feb 2024 none MIT — Details →
4.4.1 04 Dec 2023 none MIT — Details →
4.4.0 24 Aug 2023 none MIT — Details →
4.3.3 02 Aug 2023 none MIT — Details →
4.3.2 26 Jul 2023 none MIT — Details →
4.3.1 24 Jul 2023 none MIT — Details →
4.3.0 28 Apr 2023 none MIT — Details →
4.2.1 10 Feb 2023 none MIT — Details →
4.2.0 18 Jan 2023 none MIT — Details →
4.1.2 05 Jan 2023 none MIT — Details →
4.1.1 17 Dec 2022 none MIT — Details →
4.1.0 16 Dec 2022 none MIT — Details →
4.0.1 14 Nov 2022 none MIT — Details →
4.0.0-release 14 Nov 2022 none MIT — Details →
4.0.0-alpha.3 24 Oct 2022 none MIT — Details →
4.0.0-alpha.2 12 Oct 2022 none MIT — Details →
3.9.1 03 Aug 2022 none MIT — Details →
3.9.0 02 Aug 2022 none MIT — Details →
3.8.2 24 Jul 2022 none MIT — Details →
3.8.1 24 Jul 2022 none MIT — Details →
3.8.0 25 May 2022 none MIT — Details →
3.7.1 12 Feb 2022 none MIT — Details →
3.7.0 23 Dec 2021 none MIT — Details →
3.6.2 05 Dec 2021 none MIT — Details →
3.6.1 30 Nov 2021 none MIT — Details →
3.6.0 23 Oct 2021 none MIT — Details →
3.5.1 18 Aug 2021 none MIT — Details →
3.5.0 25 Jul 2021 none MIT — Details →
3.4.1 04 Jul 2021 none MIT — Details →
3.4.0 26 Jun 2021 none MIT — Details →
3.3.2 30 May 2021 none MIT — Details →
3.3.1 29 May 2021 none MIT — Details →
3.3.0 24 May 2021 none MIT — Details →
3.2.1 01 May 2021 none MIT — Details →
3.2.0 24 Apr 2021 none MIT — Details →
3.1.1 17 Apr 2021 none MIT — Details →
3.1.0 10 Apr 2021 none MIT — Details →
3.0.2 04 Apr 2021 none MIT — Details →
3.0.1 02 Apr 2021 none MIT — Details →
3.0.0 02 Apr 2021 none MIT — Details →
3.0.0-rc.7 02 Apr 2021 none MIT — Details →
3.0.0-rc.6 27 Mar 2021 none MIT — Details →
3.0.0-rc.5 25 Mar 2021 none MIT — Details →
3.0.0-rc.4 25 Mar 2021 none MIT — Details →
3.0.0-rc.3 23 Mar 2021 none MIT — Details →
3.0.0-rc.2 21 Mar 2021 none MIT — Details →
3.0.0-rc 18 Mar 2021 none MIT — Details →
3.0.0-beta.14 16 Mar 2021 none MIT — Details →
3.0.0-beta.13 06 Mar 2021 none MIT — Details →
3.0.0-beta.12 27 Feb 2021 none MIT — Details →
3.0.0-beta.11 20 Feb 2021 none MIT — Details →
3.0.0-beta.10 01 Feb 2021 none MIT — Details →
3.0.0-beta.9 16 Jan 2021 none MIT — Details →
3.0.0-beta.8 13 Jan 2021 none MIT — Details →
3.0.0-beta.7 04 Dec 2020 none MIT — Details →
3.0.0-beta.6 08 Nov 2020 none MIT — Details →
3.0.0-beta.5 01 Nov 2020 none MIT — Details →
2.9.4 18 Oct 2020 none MIT — Details →
3.0.0-beta.4 15 Oct 2020 none MIT — Details →
3.0.0-beta.3 01 Oct 2020 none MIT — Details →
3.0.0-beta.2 01 Oct 2020 none MIT — Details →
3.0.0-beta 01 Sep 2020 none MIT — Details →
3.0.0-alpha.2 17 Jul 2020 none MIT — Details →
3.0.0-alpha 12 Mar 2020 none MIT — Details →
2.9.3 14 Nov 2019 H1 MIT Yes Details →
2.9.2 02 Nov 2019 H1 MIT Yes Details →
2.9.1 27 Oct 2019 H1 MIT Yes Details →
2.9.0 26 Oct 2019 H1 MIT Yes Details →
2.8.0 14 Mar 2019 H1 MIT Yes Details →
2.8.0-rc.1 04 Mar 2019 H1 MIT Yes Details →
2.7.3 15 Oct 2018 H1 MIT Yes Details →
2.7.2 01 Mar 2018 H1 MIT Yes Details →
2.7.1 28 Oct 2017 H1 MIT Yes Details →
2.7.0 10 Sep 2017 H1 MIT Yes Details →
2.6.0 25 May 2017 H1 MIT Yes Details →
2.5.0 08 Feb 2017 H1 MIT Yes Details →
2.4.0 12 Nov 2016 H1 MIT Yes Details →
2.3.0 22 Sep 2016 H1 MIT Yes Details →
2.3.0-rc.1 21 Sep 2016 H1 MIT Yes Details →
2.2.2 27 Aug 2016 H1 MIT Yes Details →
2.2.1 30 Jul 2016 H1 MIT Yes Details →
2.2.0 28 Jul 2016 H1 MIT Yes Details →
2.2.0-rc.2 19 Jul 2016 H1 MIT Yes Details →
2.2.0-rc.1 13 Jul 2016 H1 MIT Yes Details →
2.1.6 14 Jun 2016 H1 MIT Yes Details →
2.1.5 12 Jun 2016 H1 MIT Yes Details →
2.1.4 26 May 2016 H1 MIT Yes Details →
2.1.3 12 May 2016 H1 MIT Yes Details →
2.1.2 08 May 2016 H1 MIT Yes Details →
2.1.1 07 May 2016 H1 MIT Yes Details →
2.1.0 03 May 2016 H1 — Yes Details →
2.0.2 16 Apr 2016 H1 — Yes Details →
2.0.1 16 Apr 2016 H1 — Yes Details →
2.0.0 09 Apr 2016 H1 — Yes Details →
1.1.1 05 Apr 2016 H1 — Yes Details →
1.1.0 01 Apr 2016 H1 — Yes Details →
1.0.2 10 Mar 2015 H1 — Yes Details →
1.0.1 07 Jan 2015 H1 — Yes Details →
1.0.1-beta.2 08 Jul 2014 H1 — Yes Details →

All 109 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 chart.js

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7746: Prototype pollution in chart.js 7.5 high 2.9.4 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 chart.js

Is chart.js safe to use?

Vulert records 1 vulnerabilities for chart.js in npm: 0 critical, 1 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 chart.js's Vulert package health score?

Vulert scores chart.js 84/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 chart.js affected?

No. 4.6.1, 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 chart.js have?

1 vulnerability is recorded for chart.js in the npm ecosystem: 0 critical, 1 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 chart.js vulnerabilities disclosed?

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

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