Local File Inclusion vulnerability in zmarkdown

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact A minor Local File Inclusion vulnerability has been found in zmarkdown, which allowed for images with a known path on the host machine to be included inside a LaTeX document. To prevent it, a new option has been created that allow to replace invalid paths with a default image instead of linking the image on the host directly. zmarkdown has been updated to make this setting the default. Every user of zmarkdown is likely impacted, except if disabling LaTeX generation or images download. Here is an example of including an image from an invalid path: Will effectively redownload and include the image found at /tmp/img.png. Patches The vulnerability has been patched in version 10.1.3. If impacted, you should update to this version as soon as possible. Workarounds Disable images downloading, or sanitize paths. For more information If you have any questions or comments about this advisory, open an issue in ZMarkdown.

Published by the source

3 Feb 2024, 00:37 UTC

Last modified by the source

14 May 2024, 22:01 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mq6v-w35g-3c97

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mq6v-w35g-3c97

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-mq6v-w35g-3c97

Advisory: Local File Inclusion vulnerability in zmarkdown
IDs: GHSA-mq6v-w35g-3c97
Record: https://patchnext.com/advisories/ghsa-mq6v-w35g-3c97 (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: zmarkdown 10.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm zmarkdown: affected < 10.1.3; fixed in 10.1.3

## Suggested inspection (read-only)
- `npm ls zmarkdown --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 zmarkdown.
- 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-mq6v-w35g-3c97 (OSV record GHSA-mq6v-w35g-3c97 lists affected ranges: npm zmarkdown >=0 <10.1.3 (fixed))
- Verified: https://github.com/advisories/GHSA-mq6v-w35g-3c97 (GitHub-reviewed advisory GHSA-mq6v-w35g-3c97 lists affected ranges: npm zmarkdown >=0 <10.1.3)

Commands are suggestions: review each one before running it.