Skip to main content
VulnerabilityPublished Updated

CVE-2026-14699: zcaceres markdownify-mcp · Symlink Following

Affects zcaceres markdownify-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
zcaceresmarkdownify-mcpAffected
  • =1.0
  • =1.1.0
Fixed in–
GitHubzcaceres/markdownify-mcppkg:github/zcaceres/markdownify-mcpOther threatsAffected
  • =1.0
  • =1.1.0
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:zcaceres:markdownify-mcp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the project's repository or vendor advisory for updates regarding the acceptance and release of the fix. Until then, restrict local access to trusted users only to reduce risk.

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.

References

Community reviews

Loading reviews…