# CVE-2025-65512: Server-side request forgery in n/a

> An attacker can bypass IP restrictions to access internal network services via SSRF in the markdownify-mcp library's webpage-to-markdown feature.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-pfj3-mmxr-4rjh

## What is CVE-2025-65512?

CVE-2025-65512 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-65512?

It affects 1 product.


Products: Zcaceres Markdownify Mcp Server.

## How do I fix CVE-2025-65512?

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

## Is CVE-2025-65512 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65512 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65512 and fix it if it is affected.

What it is: CVE-2025-65512 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65512 exists.

Affected product: n/a. 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-2025-65512/ (Markdown: https://insights.sbomify.com/CVE-2025-65512/index.md)
```

## Sources

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

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