# CVE-2026-14699: zcaceres markdownify-mcp Markdownify.ts assertPathAllowed symlink

> Local attackers can bypass path restrictions via symlink following in the markdownify-mcp library, potentially reading or modifying unauthorized files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-mf9r-r6pc-8fc6

## What is CVE-2026-14699?

CVE-2026-14699 is a medium-severity path traversal vulnerability in zcaceres markdownify-mcp, published on 5 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in zcaceres markdownify-mcp up to 1.1.0. The affected element is the function assertPathAllowed of the file src/Markdownify.ts. Executing a manipulation can lead to symlink following. The attack can only be executed locally. The pull request to fix this issue awaits acceptance.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following), CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-14699?


## How do I fix CVE-2026-14699?

No fix has been published for CVE-2026-14699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14699 being exploited?

There is no known exploitation of CVE-2026-14699 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14699 and fix it if it is affected.

What it is: CVE-2026-14699 is a medium-severity path traversal vulnerability in zcaceres markdownify-mcp, published on 5 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14699 in the wild and no public exploit code.

Affected product: zcaceres markdownify-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14699/ (Markdown: https://insights.sbomify.com/CVE-2026-14699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14699
- OSV: https://osv.dev/vulnerability/CVE-2026-14699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14699/
Summaries are generated and may contain mistakes; the official description above is the record.