GHSA-mf74-qq7w-6j7v
Zmarkdown Server-Side Request Forgery (SSRF) in remark-download-images
Blast Radius
remark-images-downloadReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A major blind SSRF has been found in remark-images-download, which allowed
for requests to be made to neighboring servers on local IP ranges.
The issue came from a loose filtering of URLs inside the module.
Imagine a server running on a private network 192.168.1.0/24.
A private service serving images is running on 192.168.1.2, and
is not expected to be accessed by users. A machine is running
remark-images-download on the neighboring 192.168.1.3 host.
An user enters the following Markdown:
The image is downloaded by the server and included inside the resulting document. Hence, the user has access to the private image.
It has been corrected by preventing images downloads from local IP ranges, both in IPv4 and IPv6. To avoid malicious domain names, resolved local IPs from are also forbidden inside the module. This vulnerability impact is moderate, as it is can allow access to unexposed documents on the local network, and is very easy to exploit.
Patches
The vulnerability has been patched in version 3.1.0. If impacted, you should update to this version as soon as possible.
Please note that a minor version has been released instead of a bugfix. This is due to a new option included to prevent another vulnerability, upgrading to the new version will not break compatibility.
Workarounds
No workaround is known, the package should be upgraded.
For more information
If you have any questions or comments about this advisory, open an issue in ZMarkdown.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | remark-images-download | all versions | 3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remark-images-download. 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.
Fix
Update remark-images-download to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf74-qq7w-6j7v is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-mf74-qq7w-6j7v 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-mf74-qq7w-6j7v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mf74-qq7w-6j7v in your dependencies?
O3 detects GHSA-mf74-qq7w-6j7v across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.