VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-red-dashboard: vulnerability history, versions and safety

node-red-dashboard is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 106 releases, from Oct 2019 to Nov 2022. 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 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 node-red-dashboard vulnerabilities

Vulert verdict on node-red-dashboard 3.6.6 i

Updated on 22 Oct 2026

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

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 3.6.6 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 01 Nov 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 20 packages i
  • Stars 1,407 i
  • OpenSSF scorecard 1/10 i
  • Last release 14 months ago 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 node-red-dashboard, 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
3.6.6 07 Aug 2025 none Apache-2.0 — Details →
3.6.5 12 Mar 2024 none Apache-2.0 — Details →
3.6.4 12 Mar 2024 none Apache-2.0 — Details →
3.6.3 12 Mar 2024 none Apache-2.0 — Details →
3.6.2 06 Dec 2023 none Apache-2.0 — Details →
3.6.1 19 Oct 2023 none Apache-2.0 — Details →
3.6.0 31 Aug 2023 none Apache-2.0 — Details →
3.5.0 26 May 2023 none Apache-2.0 — Details →
3.4.0 09 Mar 2023 none Apache-2.0 — Details →
3.3.1 03 Jan 2023 none Apache-2.0 — Details →
3.3.0 31 Dec 2022 none Apache-2.0 — Details →
3.2.3 23 Nov 2022 none Apache-2.0 — Details →
3.2.2 23 Nov 2022 none Apache-2.0 — Details →
3.2.0 09 Sep 2022 none Apache-2.0 — Details →
3.1.7 09 May 2022 M1 Apache-2.0 Yes Details →
3.1.6 17 Feb 2022 M1 Apache-2.0 Yes Details →
3.1.5 21 Jan 2022 M1 Apache-2.0 Yes Details →
3.1.4 14 Jan 2022 M1 Apache-2.0 Yes Details →
3.1.3 21 Dec 2021 M1 Apache-2.0 Yes Details →
3.1.2 19 Nov 2021 M1 Apache-2.0 Yes Details →
3.1.1 06 Nov 2021 M1 Apache-2.0 Yes Details →
3.1.0 26 Oct 2021 M1 Apache-2.0 Yes Details →
3.0.4 16 Sep 2021 M1 Apache-2.0 Yes Details →
3.0.3-beta 06 Sep 2021 M1 Apache-2.0 Yes Details →
3.0.2-beta 02 Sep 2021 M1 Apache-2.0 Yes Details →
3.0.1-beta 19 Aug 2021 M1 Apache-2.0 Yes Details →
2.30.0 09 Jul 2021 M1 Apache-2.0 Yes Details →
3.0.0-beta 12 Jun 2021 M1 Apache-2.0 Yes Details →
2.29.3 12 Jun 2021 M1 Apache-2.0 Yes Details →
2.29.2 11 Jun 2021 M1 Apache-2.0 Yes Details →
2.29.1 17 May 2021 M1 Apache-2.0 Yes Details →
2.29.0 23 Apr 2021 M1 Apache-2.0 Yes Details →
2.28.2 19 Mar 2021 M1 Apache-2.0 Yes Details →
2.28.1 14 Feb 2021 M1 Apache-2.0 Yes Details →
2.28.0 12 Feb 2021 M1 Apache-2.0 Yes Details →
2.27.0 19 Jan 2021 M1 Apache-2.0 Yes Details →
2.26.2 11 Jan 2021 M1 Apache-2.0 Yes Details →
2.26.1 29 Dec 2020 H1 M1 Apache-2.0 Yes Details →
2.26.0 21 Dec 2020 H1 M1 Apache-2.0 Yes Details →
2.25.0 08 Dec 2020 H1 M1 Apache-2.0 Yes Details →
2.24.2 01 Dec 2020 H1 M1 Apache-2.0 Yes Details →
2.24.1 26 Nov 2020 H1 M1 Apache-2.0 Yes Details →
2.24.1-beta 16 Nov 2020 H1 M1 Apache-2.0 Yes Details →
2.24.0 13 Nov 2020 H1 M1 Apache-2.0 Yes Details →
2.23.5 29 Oct 2020 H1 M1 Apache-2.0 Yes Details →
2.23.4 25 Sep 2020 H1 M1 Apache-2.0 Yes Details →
2.23.3 04 Sep 2020 H1 M1 Apache-2.0 Yes Details →
2.23.2 07 Aug 2020 H1 M1 Apache-2.0 Yes Details →
2.23.1 07 Aug 2020 H1 M1 Apache-2.0 Yes Details →
2.23.0 10 Jul 2020 H1 M1 Apache-2.0 Yes Details →
2.22.1 08 May 2020 H1 M1 Apache-2.0 Yes Details →
2.22.0 07 May 2020 H1 M1 Apache-2.0 Yes Details →
2.21.0 19 Apr 2020 H1 M1 Apache-2.0 Yes Details →
2.20.0 03 Apr 2020 H1 M1 Apache-2.0 Yes Details →
2.19.4 07 Feb 2020 H1 M1 Apache-2.0 Yes Details →
2.19.3 21 Dec 2019 H1 M1 Apache-2.0 Yes Details →
2.19.2 06 Dec 2019 H1 M1 Apache-2.0 Yes Details →
2.19.1 03 Dec 2019 H1 M1 Apache-2.0 Yes Details →
2.19.0 27 Nov 2019 H1 M1 Apache-2.0 Yes Details →
2.18.0 23 Nov 2019 H1 M1 Apache-2.0 Yes Details →
2.17.1 09 Oct 2019 H1 M1 Apache-2.0 Yes Details →
2.17.0 03 Oct 2019 H1 M1 Apache-2.0 Yes Details →
2.16.3 16 Sep 2019 H1 M2 Apache-2.0 Yes Details →
2.16.2 30 Aug 2019 H1 M2 Apache-2.0 Yes Details →
2.16.1 22 Aug 2019 H1 M2 Apache-2.0 Yes Details →
2.16.0 16 Aug 2019 H1 M2 Apache-2.0 Yes Details →
2.15.5 24 Jun 2019 H1 M2 Apache-2.0 Yes Details →
2.15.4 30 May 2019 H1 M2 Apache-2.0 Yes Details →
2.15.3 26 May 2019 H1 M2 Apache-2.0 Yes Details →
2.15.2 15 May 2019 H1 M2 Apache-2.0 Yes Details →
2.15.1 14 May 2019 H1 M2 Apache-2.0 Yes Details →
2.15.0 13 May 2019 H1 M2 Apache-2.0 Yes Details →
2.14.0 28 Feb 2019 H1 M2 Apache-2.0 Yes Details →
2.13.2 29 Jan 2019 H1 M2 Apache-2.0 Yes Details →
2.13.1 28 Jan 2019 H1 M2 Apache-2.0 Yes Details →
2.13.0 22 Dec 2018 H1 M2 Apache-2.0 Yes Details →
2.12.2 10 Dec 2018 H1 M2 Apache-2.0 Yes Details →
2.12.1 08 Dec 2018 H1 M2 Apache-2.0 Yes Details →
2.12.0 07 Dec 2018 H1 M2 Apache-2.0 Yes Details →
2.11.0 17 Nov 2018 H1 M2 Apache-2.0 Yes Details →
2.10.1 29 Oct 2018 H1 M2 Apache-2.0 Yes Details →
2.10.0 22 Oct 2018 H1 M2 Apache-2.0 Yes Details →
2.9.8 06 Sep 2018 H1 M2 Apache-2.0 Yes Details →
2.9.7 24 Aug 2018 H1 M2 Apache-2.0 Yes Details →
2.9.6 17 Jul 2018 H1 M2 Apache-2.0 Yes Details →
2.9.5 08 Jul 2018 H1 M2 Apache-2.0 Yes Details →
2.9.4 25 May 2018 H1 M2 Apache-2.0 Yes Details →
2.9.3 08 May 2018 H1 M2 Apache-2.0 Yes Details →
2.9.2 07 May 2018 H1 M2 Apache-2.0 Yes Details →
2.9.1 22 Apr 2018 H1 M2 Apache-2.0 Yes Details →
2.9.0 13 Apr 2018 H1 M2 Apache-2.0 Yes Details →
2.8.2 01 Mar 2018 H1 M2 Apache-2.0 Yes Details →
2.8.1 15 Feb 2018 H1 M2 Apache-2.0 Yes Details →
2.8.0 30 Jan 2018 H1 M2 Apache-2.0 Yes Details →
2.7.0 17 Dec 2017 H1 M2 Apache-2.0 Yes Details →
2.6.2 10 Nov 2017 H1 M2 Apache-2.0 Yes Details →
2.6.1 31 Oct 2017 H1 M2 Apache-2.0 Yes Details →
2.6.0 30 Oct 2017 H1 M2 Apache-2.0 Yes Details →
2.5.1 25 Sep 2017 H1 M2 Apache-2.0 Yes Details →
2.5.0 18 Sep 2017 H1 M2 Apache-2.0 Yes Details →
2.4.3 18 Jul 2017 H1 M2 — Yes Details →
2.4.2 07 Jul 2017 H1 M2 — Yes Details →
2.4.1 30 Jun 2017 H1 M2 — Yes Details →
2.4.0 30 Jun 2017 H1 M2 — Yes Details →
2.3.11 23 May 2017 H1 M2 — Yes Details →
2.3.10 05 May 2017 H1 M2 — Yes Details →
2.3.9 26 Apr 2017 H1 M2 — Yes Details →
2.3.8 17 Apr 2017 H1 M2 — Yes Details →
2.3.6 20 Mar 2017 H1 M2 — Yes Details →
2.3.5 04 Mar 2017 H1 M2 — Yes Details →
2.3.4 03 Mar 2017 H1 M2 — Yes Details →
2.3.3 22 Feb 2017 H1 M2 — Yes Details →
2.3.2 19 Feb 2017 H1 M2 — Yes Details →
2.3.1 18 Feb 2017 H1 M2 — Yes Details →
2.3.0 17 Feb 2017 H1 M2 — Yes Details →
2.2.1 22 Dec 2016 H1 M2 — Yes Details →
2.2.0 15 Dec 2016 H1 M2 — Yes Details →
2.1.0 11 Oct 2016 H1 M2 — Yes Details →
2.0.2 09 Sep 2016 H1 M2 — Yes Details →
2.0.1 29 Jul 2016 H1 M2 — Yes Details →

The newest 120 of 121 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
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for node-red-dashboard

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-3783: node-red-dashboard Cross-site Scripting Vulnerability 6.1 medium 3.2.0 01 Nov 2022
CVE-2019-10756: Cross-site Scripting in node-red-dashboard 5.4 medium 2.17.0 25 Oct 2019
CVE-2021-3223: Path Traversal in Node-RED-Dashboard N/A high 2.26.2 29 Jan 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 node-red-dashboard

Is node-red-dashboard safe to use?

Vulert records 3 vulnerabilities for node-red-dashboard in npm: 0 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 node-red-dashboard's Vulert package health score?

Vulert scores node-red-dashboard 45/100, which reads as risky. 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of node-red-dashboard affected?

No. 3.6.6, 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 node-red-dashboard should I use?

3.6.6 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 node-red-dashboard have?

3 vulnerabilities are recorded for node-red-dashboard in the npm ecosystem: 0 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 node-red-dashboard vulnerabilities disclosed?

0 vulnerabilities were recorded for node-red-dashboard in the last 12 months, and the oldest entry in this database dates to 25 Oct 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 node-red-dashboard 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 node-red-dashboard for upcoming vulnerabilities?

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