)\n```\n\n\n## Recommendation\n\nUpdate to v1.7.0 or later","image":"https://o3.security/opengraph.png","datePublished":"2018-11-09T17:48:20Z","dateModified":"2023-11-08T03:58:59.342969Z","url":"https://o3.security/vulnerability/CVE-2017-16006","inLanguage":"en","author":{"@id":"https://o3.security/#organization"},"publisher":{"@id":"https://o3.security/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://o3.security/vulnerability/CVE-2017-16006"},"speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".vuln-summary",".vuln-severity",".vuln-mitigation"]},"about":[{"@type":"SoftwareApplication","name":"remarkable","applicationCategory":"npm","softwareVersion":"1.7.0"}],"citation":[{"@type":"CreativeWork","name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16006"},{"@type":"CreativeWork","name":"OSV.dev","url":"https://osv.dev/vulnerability/CVE-2017-16006"},{"@type":"CreativeWork","url":"https://github.com/jonschlinkert/remarkable/issues/227"},{"@type":"CreativeWork","url":"https://github.com/advisories/GHSA-mrmf-qwxg-7c3h"},{"@type":"CreativeWork","url":"https://www.npmjs.com/advisories/319"}]})\n```\n\n\n## Recommendation\n\nUpdate to v1.7.0 or later","url":"https://o3.security/vulnerability/CVE-2017-16006","identifier":"CVE-2017-16006","datePublished":"2018-11-09T17:48:20Z","dateModified":"2023-11-08T03:58:59.342969Z","inLanguage":"en","license":"https://creativecommons.org/licenses/by/4.0/","keywords":["CVE-2017-16006","CWE-79","CVE","vulnerability","security advisory"],"creator":{"@id":"https://o3.security/#organization"},"isAccessibleForFree":true,"citation":[{"@type":"CreativeWork","name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16006"},{"@type":"CreativeWork","name":"OSV.dev","url":"https://osv.dev/vulnerability/CVE-2017-16006"}]})\n```\n\n\n## Recommendation\n\nUpdate to v1.7.0 or later"}},{"@type":"Question","name":"How severe is GHSA-mrmf-qwxg-7c3h?","acceptedAnswer":{"@type":"Answer","text":"No CVSS score has been assigned to GHSA-mrmf-qwxg-7c3h yet. Review the advisory details and affected package list to assess your exposure."}},{"@type":"Question","name":"Which packages are affected by GHSA-mrmf-qwxg-7c3h?","acceptedAnswer":{"@type":"Answer","text":"GHSA-mrmf-qwxg-7c3h affects the following packages: remarkable (npm). Ecosystems affected: npm."}},{"@type":"Question","name":"How do I fix GHSA-mrmf-qwxg-7c3h?","acceptedAnswer":{"@type":"Answer","text":"Update remarkable to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrmf-qwxg-7c3h is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-mrmf-qwxg-7c3h in my npm dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remarkable. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match."}},{"@type":"Question","name":"How do I mitigate GHSA-mrmf-qwxg-7c3h if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-mrmf-qwxg-7c3h?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-mrmf-qwxg-7c3h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-mrmf-qwxg-7c3h actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 2 known exploit references for GHSA-mrmf-qwxg-7c3h, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization."}},{"@type":"Question","name":"What type of vulnerability is GHSA-mrmf-qwxg-7c3h?","acceptedAnswer":{"@type":"Answer","text":"GHSA-mrmf-qwxg-7c3h is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was GHSA-mrmf-qwxg-7c3h published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-mrmf-qwxg-7c3h was published on November 9, 2018 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-mrmf-qwxg-7c3h

GHSA-mrmf-qwxg-7c3h is a Cross-site Scripting (XSS) vulnerability in remarkable. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-mrmf-qwxg-7c3h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XSS in Data URI in remarkable

Also known asCVE-2017-16006
Published
Nov 9, 2018
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

496other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
remarkablenpm
1.3Mdownloads / week

Description

Affected versions of remarkable are vulnerable to cross-site scripting. Vulnerable versions of the package allow the use of data: URIs in links, and can therefore execute javascript.

Proof of Concept

[link](data:text/html,<script>alert('0')</script>)

Recommendation

Update to v1.7.0 or later

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmremarkableall versions1.7.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remarkable. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update remarkable to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrmf-qwxg-7c3h is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-mrmf-qwxg-7c3h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mrmf-qwxg-7c3h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `remarkable` are vulnerable to cross-site scripting. Vulnerable versions of the package allow the use of `data:` URIs in links, and can therefore execute javascript. ## Proof of Concept ```markdown [link](data:text/html,<script>alert('0')</script>) ``` ## Recommendation Update to v1.7.0 or later
O3 Security · Impact-Aware SCA

Is GHSA-mrmf-qwxg-7c3h in your dependencies?

O3 detects GHSA-mrmf-qwxg-7c3h across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-mrmf-qwxg-7c3h: XSS in Data URI in… | O3 Security