Vulnerability Database · npm · remarkable · Version
remarkable 1.2.0
1.2.0 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.0.1.
Critical 0 High 3 Medium 1 Low 0 Unrated 0
-
Released 26 Oct 2014
Licence MIT
Also known from other sources 4
Newer releases 23
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
remarkable 1.2.0 vulnerabilities
4 vulnerabilities cover remarkable 1.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2019-12041: Regular Expression Denial of Service in remarkable | 7.5 high | 1.7.2 | 06 Jun 2019 |
| CVE-2019-12043: Cross-site Scripting in remarkable | 6.1 medium | 1.7.2 | 29 May 2019 |
| CVE-2014-10065: Content Injection in remarkable | N/A high | 1.4.1 | 31 Aug 2020 |
| CVE-2017-16006: XSS in Data URI in remarkable | N/A high | 1.7.0 | 09 Nov 2018 |
Looking for another version, or everything Vulert holds for remarkable?
Questions
About remarkable 1.2.0
Is remarkable 1.2.0 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover remarkable 1.2.0: 0 critical, 3 high, 1 medium and 0 low. The upgrade Vulert recommends is 2.0.1, and each entry above names the fixed version to move to.
Which version of remarkable should I use instead of 1.2.0?
2.0.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.2.0 the latest release of remarkable?
No. 1.2.0 was published 26 Oct 2014, 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 remarkable for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the remarkable version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.