GHSA-mq6v-w35g-3c97 — zmarkdown
GHSA-mq6v-w35g-3c97 is a security vulnerability in zmarkdown. A fix is available for zmarkdown — see the affected versions and patch details below.
Local File Inclusion vulnerability in zmarkdown
Real-World Exposure
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.
zmarkdownnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | zmarkdown | all versions | 10.1.3npm install zmarkdown@10.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zmarkdown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zmarkdown to 10.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mq6v-w35g-3c97 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mq6v-w35g-3c97 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mq6v-w35g-3c97. 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-mq6v-w35g-3c97 in your dependencies?
O3 Security finds GHSA-mq6v-w35g-3c97 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.