# CVE-2025-26240: pdfkit: Path traversal in from_string

> Attackers can execute arbitrary JavaScript and read local files via the from_string method in python-pdfkit, requiring an upgrade to mitigate.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** CLSA-2026-1772496734, DEBIAN-CVE-2025-26240, GHSA-9g3x-6x24-vf9f, PYSEC-2026-2860, UBUNTU-CVE-2025-26240

## What is CVE-2025-26240?

CVE-2025-26240 is a high-severity code injection vulnerability in n/a, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In JazzCore python-pdfkit 1.0.0, the from_string method enables the execution of JavaScript code within the context of the server application and the exfiltration of local files.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

3 open source packages ship an affected version, including pdfkit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pdfkit` | PyPI | All versions to 1.0.0 | None |
| `pdfkit` | PyPI | All versions to 1.0.0 | None |
| `pdfkit` | PyPI | All versions to 1.0.0 | None |

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

Upgrade to a fixed version.

## Is CVE-2025-26240 being exploited?

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

Public exploit code:

- POC for CVE-2025-26240 (github_poc): https://github.com/Habuon/CVE-2025-26240

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26240 is a high-severity code injection vulnerability in n/a, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26240 exists.

Affected packages and fixed versions:
- pdfkit (PyPI): affected all versions up to 1.0.0; no fix listed
- pdfkit (PyPI): affected all versions up to 1.0.0; no fix listed
- pdfkit (PyPI): affected all versions up to 1.0.0; no fix listed

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

## Sources

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

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