Security readout for executives and security teams
Plain-English summary
Remarkable, a Node.js Markdown parser, allowed unsafe data: links in versions 1.6.2 and earlier. If an application renders untrusted Markdown with this parser, a crafted link could lead to browser-side script execution in that application’s context.
Executive priority
Address during normal vulnerability remediation, faster if customer, employee, or admin-facing pages render user-provided Markdown with affected versions.
Technical view
CVE-2017-16006 is a CWE-79 cross-site scripting issue in the remarkable node module. The provided record says versions <=1.6.2 allow data: URIs in links, which can enable JavaScript execution when rendered Markdown is viewed.
Likely exposure
Exposure is most likely in web applications, documentation portals, comment systems, or CMS workflows that use remarkable <=1.6.2 to render user-controlled Markdown.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitability depends on whether attackers can supply Markdown that is rendered for other users in a browser.
Researcher notes
The available evidence is limited to the CVE description and referenced advisories. No CVSS score, confirmed fixed version, or active exploitation evidence is provided in the source bundle.
Mitigation direction
- Inventory projects for the remarkable node module and affected versions.
- Check current vendor or package guidance before choosing an upgrade or replacement path.
- Prioritize remediation where untrusted Markdown is rendered to authenticated or administrative users.
- Restrict affected Markdown rendering paths until remediation is complete.
Validation and detection
- Review package manifests and lockfiles for remarkable versions <=1.6.2.
- Identify routes or features that render user-supplied Markdown through remarkable.
- Confirm rendered links reject unsafe URI schemes after remediation.
- Add regression tests for Markdown link sanitization behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-16006 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jonschlinkert/remarkable/issues/227CVE reference · x_refsource_MISC
- https://nodesecurity.io/advisories/319CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.