# CVE-2026-13150: SSRF in Pentestify PDF generation endpoint via Host header

> Remote attackers can exploit SSRF in Pentestify's PDF generation endpoint via a crafted Host header to access internal resources and cloud metadata.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-jmg8-x6hq-972w

## What is CVE-2026-13150?

CVE-2026-13150 is a medium-severity server-side request forgery vulnerability in Pentestify, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) (CWE-918) in the PDF generation endpoint GET /api/reports/{id}/pdf (backend/main.py) in ccyl13 Pentestify 1.0.0 and lower allows remote attackers to make the server issue requests to arbitrary internal or external URLs, including cloud metadata services, and return the rendered content in the resulting PDF via a crafted Host header, because the target URL is built from request.base_url without validation.

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

## Which versions are affected by CVE-2026-13150?


## How do I fix CVE-2026-13150?

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

## Is CVE-2026-13150 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13150 and fix it if it is affected.

What it is: CVE-2026-13150 is a medium-severity server-side request forgery vulnerability in Pentestify, published on 24 Jun 2026. 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-2026-13150 in the wild and no public exploit code.

Affected product: Pentestify. 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-2026-13150/ (Markdown: https://insights.sbomify.com/CVE-2026-13150/index.md)
```

## Sources

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

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