Zmarkdown Server-Side Request Forgery (SSRF) in remark-download-images
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (remark-images-download 3.1.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 3.1.0
- Fixed in
- 3.1.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-mf74-qq7w-6j7v lists affected ranges: npm remark-images-download >=0 <3.1.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mf74-qq7w-6j7v lists affected ranges: npm remark-images-download >=0 <3.1.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-mf74-qq7w-6j7v
- Revision 1 · created ·
Published from osv record GHSA-mf74-qq7w-6j7v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-mf74-qq7w-6j7v Advisory: Zmarkdown Server-Side Request Forgery (SSRF) in remark-download-images IDs: GHSA-mf74-qq7w-6j7v Record: https://patchnext.com/advisories/ghsa-mf74-qq7w-6j7v (revision 2, source checked 26 Oct 2026, 12:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: remark-images-download 3.1.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm remark-images-download: affected < 3.1.0; fixed in 3.1.0 ## Suggested inspection (read-only) - `npm ls remark-images-download --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on remark-images-download. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-mf74-qq7w-6j7v (OSV record GHSA-mf74-qq7w-6j7v lists affected ranges: npm remark-images-download >=0 <3.1.0 (fixed)) - Verified: https://github.com/advisories/GHSA-mf74-qq7w-6j7v (GitHub-reviewed advisory GHSA-mf74-qq7w-6j7v lists affected ranges: npm remark-images-download >=0 <3.1.0) Commands are suggestions: review each one before running it.
Loading voting…