# CVE-2026-115729: @pdfme/common 5.5.10 before 6.2.6 SSRF via isUrlSafeToFetch Bypass


- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wf6h-pqhw-phmv

## What is CVE-2026-115729?

CVE-2026-115729 is a high-severity vulnerability in pdfme common, published on 23 Oct 2026. 

### Official description

@pdfme/common from 5.5.10 before 6.2.6 contains a server-side request forgery vulnerability that allows attackers to bypass the isUrlSafeToFetch denylist in getB64BasePdf. Attackers can supply basePdf URLs using IPv4-mapped IPv6, [::], NAT64 or localhost alias hostnames to read loopback, internal or cloud metadata responses through generated documents.

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

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


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

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

## Is CVE-2026-115729 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115729 is a high-severity vulnerability in pdfme common, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115729 exists.

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

## Sources

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

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