# CVE-2026-63630: BentoPDF: Workflow Import Allows Unvalidated TSA URL Leading to PDF Hash Exfiltration via RFC 3161 Requests

> Attackers can exfiltrate PDF hashes via unvalidated TSA URLs in imported workflows, enabling document correlation and confirmation.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-cx8x-7rrr-r9x8

## What is CVE-2026-63630?

CVE-2026-63630 is a low-severity server-side request forgery vulnerability in alam00000 bentopdf, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

BentoPDF is a client-side PDF toolkit that is self hostable. In 2.8.6 and earlier, deserializeWorkflow() accepts the Timestamp node's tsaUrl control from imported JSON without schema or destination validation. When a user imports the crafted workflow and runs it against a PDF, timestampPdf() sends an RFC 3161 TimeStampReq containing the PDF's SHA-256 MessageImprint to the attacker-selected endpoint. The default self-hosted configuration does not set VITE_CORS_PROXY_URL, so the request bypasses the proxy's ALLOWED_TSA_HOSTS checks and is sent directly. The disclosed digest can confirm that a document matches a known file and can correlate the same document across users without revealing its contents. This vulnerability is fixed in 2.8.7.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-63630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63630 is a low-severity server-side request forgery vulnerability in alam00000 bentopdf, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63630 exists.

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

## Sources

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

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