VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

canvas: vulnerability history, versions and safety

canvas is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 59 releases, from Jun 2019 to 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
2 vulnerabilities recorded H1 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 canvas vulnerabilities

Vulert verdict on canvas 3.2.3 i

Updated on 22 Oct 2026

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

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

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

  • Current release 3.2.3 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 07 May 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 1,556 packages i
  • Stars 10,696 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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 canvas, 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.0.0-rc3 15 Aug 2026 none MIT — Details →
4.0.0-rc2 07 Aug 2026 none MIT — Details →
4.0.0-rc1 20 Jul 2026 none MIT — Details →
3.2.3 31 Mar 2026 none MIT — Details →
3.2.2 21 Mar 2026 none MIT — Details →
3.2.1 10 Jan 2026 none MIT — Details →
3.2.0 19 Aug 2025 none MIT — Details →
3.1.2 26 Jun 2025 none MIT — Details →
3.1.1 19 Jun 2025 none MIT — Details →
3.1.0 22 Jan 2025 none MIT — Details →
3.0.1 31 Dec 2024 none MIT — Details →
3.0.0 23 Dec 2024 none MIT — Details →
3.0.0-rc3 07 Dec 2024 none MIT — Details →
3.0.0-rc2 20 Jun 2024 none MIT — Details →
3.0.0-rc1e 20 Jun 2024 none MIT — Details →
3.0.0-rc1d 19 Jun 2024 none MIT — Details →
3.0.0-rc1c 19 Jun 2024 none MIT — Details →
3.0.0-rc1b 19 Jun 2024 none MIT — Details →
2.11.1 02 Apr 2023 none MIT — Details →
2.11.2 02 Apr 2023 none MIT — Details →
2.11.0 22 Dec 2022 none MIT — Details →
2.10.2 30 Oct 2022 none MIT — Details →
2.10.1 07 Sep 2022 none MIT — Details →
2.10.0 04 Sep 2022 none MIT — Details →
2.9.3 24 Jun 2022 none MIT — Details →
2.9.2 23 Jun 2022 none MIT — Details →
2.9.1 19 Mar 2022 none MIT — Details →
2.9.0 17 Jan 2022 none MIT — Details →
2.8.0 17 May 2021 none MIT — Details →
2.7.0 01 Mar 2021 none MIT — Details →
2.6.1 06 Oct 2019 none MIT — Details →
2.6.0 11 Jun 2019 none MIT — Details →
2.5.0 01 May 2019 none MIT — Details →
2.4.1 19 Mar 2019 none MIT — Details →
2.4.0 14 Mar 2019 none MIT — Details →
2.3.1 14 Jan 2019 none MIT — Details →
2.3.0 11 Jan 2019 none MIT — Details →
2.2.0 03 Dec 2018 none MIT — Details →
2.1.0 07 Nov 2018 none MIT — Details →
2.0.1 16 Oct 2018 none MIT — Details →
2.0.0-alpha.18 10 Oct 2018 none MIT — Details →
1.6.13 10 Oct 2018 none MIT — Details →
2.0.0-alpha.17 29 Sep 2018 none MIT — Details →
2.0.0-alpha.16 25 Sep 2018 none MIT — Details →
2.0.0-alpha.15 25 Sep 2018 none MIT — Details →
1.6.12 08 Sep 2018 none MIT — Details →
2.0.0-alpha.14 08 Sep 2018 none MIT — Details →
2.0.0-alpha.13 02 Aug 2018 none MIT — Details →
1.6.11 15 May 2018 none MIT — Details →
1.6.10 22 Mar 2018 H1 MIT Yes Details →
2.0.0-alpha.12 22 Mar 2018 none MIT — Details →
2.0.0-alpha.11 09 Mar 2018 none MIT — Details →
2.0.0-alpha.10 07 Mar 2018 none MIT — Details →
2.0.0-alpha.9 27 Dec 2017 none MIT — Details →
1.6.9 21 Dec 2017 H1 M1 MIT Yes Details →
1.6.8 12 Dec 2017 H1 M1 MIT Yes Details →
2.0.0-alpha.8 12 Dec 2017 none MIT — Details →
2.0.0-alpha.7 04 Dec 2017 none MIT — Details →
2.0.0-alpha.6 06 Nov 2017 none MIT — Details →
1.6.7 08 Sep 2017 H1 M1 MIT Yes Details →
2.0.0-alpha.5 05 Sep 2017 none MIT — Details →
2.0.0-alpha.4 29 Aug 2017 none MIT — Details →
2.0.0-alpha.3 28 Aug 2017 none MIT — Details →
1.6.6 31 Jul 2017 H1 M1 MIT Yes Details →
2.0.0-alpha.2 06 May 2017 none MIT — Details →
2.0.0-alpha.1 03 May 2017 none MIT — Details →
1.6.5 18 Mar 2017 H1 M1 MIT Yes Details →
1.6.4 26 Feb 2017 H1 M1 MIT Yes Details →
1.6.3 14 Feb 2017 H1 M1 MIT Yes Details →
1.6.2 30 Oct 2016 H1 M1 MIT Yes Details →
1.6.1 23 Oct 2016 H1 M1 MIT Yes Details →
1.6.0 16 Oct 2016 H1 M1 MIT Yes Details →
1.5.0 11 Sep 2016 H1 M1 MIT Yes Details →
1.4.0 20 Jun 2016 H1 M1 MIT Yes Details →
1.3.16 29 May 2016 H1 M1 MIT Yes Details →
1.3.15 09 May 2016 H1 M1 MIT Yes Details →
1.3.14 05 May 2016 H1 M1 MIT Yes Details →
1.3.13 01 May 2016 H1 M1 MIT Yes Details →
1.3.12 01 Mar 2016 H1 M1 MIT Yes Details →
1.3.11 01 Mar 2016 H1 M1 MIT Yes Details →
1.3.10 07 Feb 2016 H1 M1 MIT Yes Details →
1.3.9 27 Jan 2016 H1 M1 MIT Yes Details →
1.3.8 22 Jan 2016 H1 M1 MIT Yes Details →
1.3.7 13 Jan 2016 H1 M1 MIT Yes Details →
1.3.6 05 Jan 2016 H1 M1 MIT Yes Details →
1.3.5 07 Dec 2015 H1 M1 MIT Yes Details →
1.3.4 21 Nov 2015 H1 M1 MIT Yes Details →
1.3.3 21 Nov 2015 H1 M1 MIT Yes Details →
1.3.2 18 Nov 2015 H1 M1 MIT Yes Details →
1.3.1 09 Nov 2015 H1 M1 MIT Yes Details →
1.3.0 26 Oct 2015 H1 M1 MIT Yes Details →
1.2.11 19 Oct 2015 H1 M1 MIT Yes Details →
1.2.10 12 Oct 2015 H1 M1 MIT Yes Details →
1.2.9 14 Sep 2015 H1 M1 MIT Yes Details →
1.2.8 30 Aug 2015 H1 M1 MIT Yes Details →
1.2.7 29 Jul 2015 H1 M1 MIT Yes Details →
1.2.6 29 Jul 2015 H1 M1 MIT Yes Details →
1.2.5 28 Jul 2015 H1 M1 MIT Yes Details →
1.2.4 23 Jul 2015 H1 M1 MIT Yes Details →
1.2.3 22 May 2015 H1 M1 MIT Yes Details →
1.2.2 20 Apr 2015 H1 M1 — Yes Details →
1.2.1 10 Feb 2015 H1 M1 — Yes Details →
1.2.0 31 Jan 2015 H1 M1 — Yes Details →
1.1.6 02 Aug 2014 H1 M1 — Yes Details →
1.1.5 26 Jun 2014 H1 M1 — Yes Details →
1.1.4 08 Jun 2014 H1 M1 — Yes Details →
1.1.3 08 Jan 2014 H1 M1 — Yes Details →
1.1.2 31 Oct 2013 H1 M1 — Yes Details →
1.1.1 09 Oct 2013 H1 M1 — Yes Details →
1.1.0 01 Aug 2013 H1 M1 — Yes Details →
1.0.4 24 Jul 2013 H1 M1 — Yes Details →
1.0.3 04 Jun 2013 H1 M1 — Yes Details →
1.0.2 23 Mar 2013 H1 M1 — Yes Details →
1.0.1 25 Feb 2013 H1 M1 — Yes Details →
1.0.0 16 Jan 2013 H1 M1 — Yes Details →
0.13.1 20 Aug 2012 H1 M1 — Yes Details →
0.13.0 13 Aug 2012 H1 M1 — Yes Details →
0.12.1 29 Jun 2012 H1 M1 — Yes Details →
0.12.0 02 May 2012 H1 M1 — Yes Details →
0.11.3 26 Apr 2012 H1 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for canvas

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8215: Buffer overflow in canvas 8.8 high 1.6.11 07 May 2021
Denial of Service in canvas N/A medium 1.6.10 05 Jun 2019

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 canvas

Is canvas safe to use?

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

Vulert scores canvas 81/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 canvas affected?

No. 3.2.3, 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 canvas should I use?

3.2.3 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 canvas have?

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

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

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