VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

joplin: vulnerability history, versions and safety

joplin is a package in the npm ecosystem. Vulert records 14 vulnerabilities for it across 120 releases, from Oct 2020 to Nov 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C2 H2 M10
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 joplin vulnerabilities

Vulert verdict on joplin 3.7.1 i

Updated on 23 Oct 2026

Careful: 3.7.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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 3.7.1 — affected i
  • Vulnerabilities on record 14 over 4 years · 0 in the last year i
  • Latest disclosure 14 Nov 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 2 packages i
  • Stars 56,750 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence AGPL-3.0-or-later 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 joplin, 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.7.1 07 Sep 2026 H1 AGPL-3.0-or-later No Details →
3.6.2 08 May 2026 H1 AGPL-3.0-or-later No Details →
3.5.1 18 Oct 2025 H1 AGPL-3.0-or-later No Details →
3.4.1 27 Aug 2025 H1 AGPL-3.0-or-later No Details →
3.3.1 01 May 2025 H1 AGPL-3.0-or-later No Details →
3.2.3 16 Jan 2025 H1 AGPL-3.0-or-later No Details →
3.2.2 12 Dec 2024 H1 AGPL-3.0-or-later No Details →
3.2.1 12 Dec 2024 H1 AGPL-3.0-or-later No Details →
3.0.1 02 Jul 2024 H2 AGPL-3.0-or-later No Details →
2.14.1 01 Mar 2024 H1 AGPL-3.0-or-later No Details →
2.13.2 30 Nov 2023 H1 AGPL-3.0-or-later No Details →
2.13.1 09 Nov 2023 H1 AGPL-3.0-or-later No Details →
2.12.1 23 Aug 2023 H1 AGPL-3.0-or-later No Details →
2.11.1 27 Jun 2023 H1 M2 AGPL-3.0-or-later No Details →
2.10.3 26 Feb 2023 H1 M2 AGPL-3.0-or-later No Details →
2.10.2 26 Feb 2023 H1 M2 AGPL-3.0-or-later No Details →
2.10.1 25 Feb 2023 H1 M2 AGPL-3.0-or-later No Details →
2.9.1 12 Oct 2022 H1 M3 MIT No Details →
2.8.1 18 May 2022 C1 H1 M3 MIT No Details →
2.6.2 17 Dec 2021 C2 H1 M3 MIT No Details →
2.6.1 03 Nov 2021 C2 H1 M3 MIT No Details →
2.4.1 29 Sep 2021 C2 H1 M3 MIT No Details →
2.3.2 16 Aug 2021 C2 H1 M3 MIT No Details →
2.2.2 11 Aug 2021 C2 H1 M4 MIT No Details →
2.2.1 10 Aug 2021 C2 H1 M4 MIT No Details →
2.1.2 27 Jun 2021 C2 H1 M4 MIT No Details →
2.1.1 27 Jun 2021 C2 H1 M4 MIT No Details →
2.0.1 16 Jun 2021 C2 H1 M5 MIT No Details →
1.8.1 10 May 2021 C2 H1 M6 MIT No Details →
1.6.4 21 Jan 2021 C2 H1 M6 MIT No Details →
1.6.3 11 Jan 2021 C2 H1 M6 MIT No Details →
1.6.2 11 Jan 2021 C2 H1 M6 MIT No Details →
1.6.1 11 Jan 2021 C2 H1 M6 MIT No Details →
1.5.1 26 Dec 2020 C2 H1 M6 MIT No Details →
1.4.9 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.8 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.7 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.6 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.5 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.4 26 Nov 2020 C2 H1 M6 MIT No Details →
1.4.3 06 Nov 2020 C2 H1 M6 MIT No Details →
1.4.2 06 Nov 2020 C2 H1 M6 MIT No Details →
1.3.3 23 Oct 2020 C2 H1 M7 MIT No Details →
1.3.2 23 Oct 2020 C2 H1 M7 MIT No Details →
1.3.1 23 Oct 2020 C2 H1 M7 MIT No Details →
1.2.3 09 Oct 2020 C2 H1 M7 MIT No Details →
1.2.2 29 Sep 2020 C2 H1 M7 MIT No Details →
1.2.1 23 Sep 2020 C2 H1 M7 MIT No Details →
1.1.8 21 Sep 2020 C2 H1 M8 MIT No Details →
1.1.7 21 Sep 2020 C2 H1 M8 MIT No Details →
1.1.2 21 Sep 2020 C2 H1 M9 MIT No Details →
1.0.168 14 Sep 2020 C2 H1 M8 MIT No Details →
1.0.167 04 Sep 2020 C2 H1 M8 MIT No Details →
1.0.166 02 Aug 2020 C2 H1 M8 MIT No Details →
1.0.165 10 Jul 2020 C2 H1 M8 MIT No Details →
1.0.164 13 May 2020 C2 H1 M8 MIT No Details →
1.0.163 10 Apr 2020 C2 H1 M8 MIT No Details →
1.0.162 01 Apr 2020 C2 H1 M8 MIT No Details →
1.0.161 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.160 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.159 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.158 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.157 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.156 07 Mar 2020 C2 H1 M8 MIT No Details →
1.0.155 08 Feb 2020 C2 H1 M8 MIT No Details →
1.0.154 07 Feb 2020 C2 H1 M8 MIT No Details →
1.0.153 24 Jan 2020 C2 H1 M8 MIT No Details →
1.0.152 24 Jan 2020 C2 H1 M8 MIT No Details →
1.0.151 24 Jan 2020 C2 H1 M8 MIT No Details →
1.0.150 11 Nov 2019 C2 H1 M8 MIT No Details →
1.0.149 27 Sep 2019 C2 H1 M8 MIT No Details →
1.0.148 27 Sep 2019 C2 H1 M8 MIT No Details →
1.0.147 25 Sep 2019 C2 H1 M8 MIT No Details →
1.0.146 08 Sep 2019 C2 H1 M8 MIT No Details →
1.0.145 08 Sep 2019 C2 H1 M8 MIT No Details →
1.0.144 08 Sep 2019 C2 H1 M8 MIT No Details →
1.0.143 08 Sep 2019 C2 H1 M8 MIT No Details →
1.0.142 08 Sep 2019 C2 H1 M8 MIT No Details →
1.0.141 28 Jul 2019 C2 H1 M8 MIT No Details →
1.0.140 10 Jun 2019 C2 H1 M8 MIT No Details →
1.0.139 05 Jun 2019 C2 H1 M8 MIT No Details →
1.0.137 19 May 2019 C2 H1 M8 MIT No Details →
1.0.136 19 May 2019 C2 H1 M8 MIT No Details →
1.0.135 13 May 2019 C2 H1 M8 MIT No Details →
1.0.133 13 May 2019 C2 H1 M8 MIT No Details →
1.0.132 13 May 2019 C2 H1 M8 MIT No Details →
1.0.131 13 May 2019 C2 H1 M8 MIT No Details →
1.0.130 13 May 2019 C2 H1 M8 MIT No Details →
1.0.129 13 May 2019 C2 H1 M8 MIT No Details →
1.0.128 13 May 2019 C2 H1 M8 MIT No Details →
1.0.127 13 May 2019 C2 H1 M8 MIT No Details →
1.0.126 12 May 2019 C2 H1 M8 MIT No Details →
1.0.125 29 Apr 2019 C2 H1 M8 MIT No Details →
1.0.124 11 Mar 2019 C2 H1 M8 MIT No Details →
1.0.123 10 Feb 2019 C2 H1 M8 MIT No Details →
1.0.122 10 Feb 2019 C2 H1 M8 MIT No Details →
1.0.120 10 Jan 2019 C2 H1 M8 MIT No Details →
1.0.119 19 Dec 2018 C2 H1 M8 MIT No Details →
1.0.118 20 Nov 2018 C2 H1 M8 MIT No Details →
1.0.117 29 Oct 2018 C2 H1 M8 MIT No Details →
1.0.116 30 Sep 2018 C2 H1 M8 — No Details →
1.0.115 28 Sep 2018 C2 H1 M8 — No Details →
1.0.114 05 Sep 2018 C2 H1 M8 — No Details →
1.0.113 25 Jul 2018 C2 H1 M8 — No Details →
1.0.112 25 Jul 2018 C2 H1 M8 — No Details →
1.0.110 30 Jun 2018 C2 H1 M8 — No Details →
1.0.109 28 Jun 2018 C2 H1 M8 — No Details →
1.0.108 14 Jun 2018 C2 H1 M8 — No Details →
1.0.107 11 May 2018 C2 H1 M8 — No Details →
1.0.106 27 Mar 2018 C2 H1 M8 — No Details →
1.0.104 23 Mar 2018 C2 H1 M8 — No Details →
1.0.103 16 Mar 2018 C2 H1 M8 — No Details →
1.0.101 16 Mar 2018 C2 H1 M8 — No Details →
1.0.100 28 Feb 2018 C2 H1 M8 — No Details →
1.0.99 19 Feb 2018 C2 H1 M8 — No Details →
1.0.98 16 Feb 2018 C2 H1 M8 — No Details →
1.0.97 16 Feb 2018 C2 H1 M8 — No Details →
1.0.96 15 Feb 2018 C2 H1 M8 — No Details →
1.0.95 12 Feb 2018 C2 H1 M8 — No Details →
0.10.93 06 Feb 2018 C2 H1 M9 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 3
  • 2022 6
  • 2023 3
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for joplin

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23340: Joplin Vulnerable to Code Injection 9.8 critical 2.7.1 09 Feb 2022
CVE-2022-35131: Arbitrary Code Execution in Joplin 9.0 critical 2.9.1 26 Jul 2022
CVE-2022-40277: Joplin Remote Code Execution 7.8 high No fix published 01 Oct 2022
CVE-2024-49362: Joplin Remote Code Execution via Unsanitized Links in Markdown Preview 7.7 high 3.1.0 14 Nov 2024
CVE-2018-1000534: Joplin Vulnerable to Cross-site Scripting in Note Content 6.1 medium 1.0.90 14 May 2022

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 joplin

Is joplin safe to use?

Vulert records 14 vulnerabilities for joplin in npm: 2 critical, 2 high, 10 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is joplin's Vulert package health score?

Vulert scores joplin 60/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 joplin affected?

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

Which version of joplin should I use?

3.7.1 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 joplin have?

14 vulnerabilities are recorded for joplin in the npm ecosystem: 2 critical, 2 high, 10 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 joplin vulnerabilities disclosed?

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

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