# CVE-2025-55150: Stirling-PDF SSRF vulnerability on /api/v1/convert/html/pdf

> Attackers can bypass sanitization in the HTML-to-PDF conversion endpoint to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** GHSA-xw8v-9mfm-g2pm

## What is CVE-2025-55150?

CVE-2025-55150 is a high-severity server-side request forgery vulnerability in Stirling-Tools Stirling-PDF, published on 11 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stirling-PDF is a locally hosted web application that performs various operations on PDF files. Prior to version 1.1.0, when using the /api/v1/convert/html/pdf endpoint to convert HTML to PDF, the backend calls a third-party tool to process it and includes a sanitizer for security sanitization which can be bypassed and result in SSRF. This issue has been patched in version 1.1.0.

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

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

It affects 1 product.


Products: Stirlingpdf Stirling Pdf.

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

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

## Is CVE-2025-55150 being exploited?

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

Public exploit code:

- Stirling-PDF < 1.1.0 - Server-Side Request Forgery (nuclei): http/cves/2025/CVE-2025-55150.yaml

## Other vulnerabilities in Stirling-Tools Stirling-PDF

- [CVE-2025-55151](https://insights.sbomify.com/CVE-2025-55151/): Stirling-PDF SSRF vulnerability on /api/v1/convert/file/pdf (high 8.6)
- [CVE-2025-55161](https://insights.sbomify.com/CVE-2025-55161/): Stirling-PDF SSRF vulnerability on /api/v1/convert/markdown/pdf (high 8.6)
- [CVE-2025-46568](https://insights.sbomify.com/CVE-2025-46568/): Stirling-PDF Server-Side Request Forgery (SSRF)-Induced Arbitrary File Read Vulnerability (high 7.7)
- [CVE-2026-33436](https://insights.sbomify.com/CVE-2026-33436/): Stirling-PDF: Reflected XSS through crafted filename in file upload functionality (low 3.1)
- [CVE-2024-9075](https://insights.sbomify.com/CVE-2024-9075/): Stirling-Tools Stirling-PDF Markdown-to-PDF cross site scripting (low 2.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55150 is a high-severity server-side request forgery vulnerability in Stirling-Tools Stirling-PDF, published on 11 Aug 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-55150 exists.

Affected product: Stirling-Tools Stirling-PDF. 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-55150/ (Markdown: https://insights.sbomify.com/CVE-2025-55150/index.md)
```

## Sources

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

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