Skip to main content
CVE-2025-65512VulnerabilityPublished Updated

CVE-2025-65512: markdownify-mcp · n/a

Affects markdownify-mcpSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
npmmarkdownify-mcppkg:npm/markdownify-mcpOther threatsAffected
  • <=0.0.2
Fixed in–

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

AI-suggested

To mitigate CVE-2025-65512, European organizations should take several specific actions beyond generic SSRF defenses: 1) Immediately audit all instances of markdownify-mcp usage, especially versions 0.0.2 and earlier, and restrict or disable the webpage-to-markdown conversion feature if possible until patched. 2) Implement strict outbound request filtering on servers running markdownify-mcp, limiting HTTP requests to only trusted external domains and blocking private IP ranges at the network or application firewall level. 3) Enforce robust hostname validation and avoid following HTTP redirects blindly during URL fetching to prevent redirect chain bypasses. 4) Monitor logs for unusual internal network access patterns originating from markdownify-mcp processes or related services. 5) Employ network segmentation and zero-trust principles to minimize the impact of any SSRF exploitation by isolating sensitive internal services. 6) Engage with the markdownify-mcp maintainers or community to track patch releases and apply updates promptly once available. 7) Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to block suspicious requests. 8) Educate developers and security teams about SSRF risks and secure coding practices related to URL fetching and content processing.

Description

A Server-Side Request Forgery (SSRF) vulnerability was discovered in the webpage-to-markdown conversion feature of markdownify-mcp v0.0.2 and before. This vulnerability allows an attacker to bypass private IP restrictions through hostname-based bypass and HTTP redirect chains, enabling access to internal network services.

References

Community reviews

Loading reviews…