The Remarkable Project maintains a focused digital-note application that has attracted a modestly represented vulnerability footprint, with exposure centered on application-layer input-handling and code-generation issues including cross-site scripting, code injection, and inefficient regular expression complexity. Current exploitation activity, severity distribution, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Remarkable Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-12041HIGH lib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA section. | May 13, 2019 | 7.5 | 24 | NO | NO |
CVE-2019-12043MEDIUM In remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a \x0ejavascript: URL. | May 13, 2019 | 6.1 | 20 | NO | NO |
CVE-2017-16006MEDIUM Remarkable is a markdown parser. In versions 1.6.2 and lower, remarkable allows the use of `data:` URIs in links and can therefore execute javascript. | Jun 4, 2018 | 6.1 | 20 | NO | NO |
CVE-2014-10065MEDIUM Certain input when passed into remarkable before 1.4.1 will bypass the bad protocol check that disallows the javascript: scheme allowing for javascript: url's to be injected into t | May 31, 2018 | 6.1 | 18 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Remarkable Project.
Media articles that mention a CVE ID that affects a product developed by Remarkable Project — matched by CVE ID, not by vendor name.