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

> Attackers can exploit SSRF in Pandoc via crafted iframes to access internal infrastructure, mitigated by using sandbox mode or pandoc-server.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 11 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** DEBIAN-CVE-2025-51591, GHSA-mcv3-ch54-xqfh, UBUNTU-CVE-2025-51591

## What is CVE-2025-51591?

CVE-2025-51591 is a low-severity server-side request forgery vulnerability in n/a, published on 11 Jul 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) in JGM Pandoc v3.6.4 allows attackers to gain access to and compromise the whole infrastructure via injecting a crafted iframe. Note: Some users have stated that Pandoc by default can retrieve and parse untrusted HTML content which can enable SSRF vulnerabilities. Using the ‘--sandbox’ option or ‘pandoc-server’ can mitigate such vulnerabilities. Using pandoc with an external ‘--pdf-engine’ can also enable SSRF vulnerabilities, such as CVE-2022-35583 in wkhtmltopdf.

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

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


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

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

## Is CVE-2025-51591 being exploited?

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

Public exploit code:

- CVE-2025-51591 Pandoc SSRF vulnerability Proof of Concept (github_poc): https://github.com/Malayke/CVE-2025-51591-Pandoc-SSRF-POC

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51591 is a low-severity server-side request forgery vulnerability in n/a, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-51591 in the wild and no public exploit code.

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-51591/ (Markdown: https://insights.sbomify.com/CVE-2025-51591/index.md)
```

## Sources

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

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