Vulnerability Database · npm · joplin · Version
joplin 1.0.162
1.0.162 is affected by 11 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.7.1.
Critical 2 High 1 Medium 8 Low 0 Unrated 0
-
Released 01 Apr 2020
Licence MIT
Also known from other sources 11
Newer releases 208
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
joplin 1.0.162 vulnerabilities
11 vulnerabilities cover joplin 1.0.162. Scroll the table for all of them, or open the full list in the database.
Looking for another version, or everything Vulert holds for joplin?
Questions
About joplin 1.0.162
Is joplin 1.0.162 vulnerable?
Yes. 11 vulnerabilities in the Vulert database cover joplin 1.0.162: 2 critical, 1 high, 8 medium and 0 low. The upgrade Vulert recommends is 3.7.1, and each entry above names the fixed version to move to.
Which version of joplin should I use instead of 1.0.162?
3.7.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.0.162 the latest release of joplin?
No. 1.0.162 was published 01 Apr 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.