CVE-2025-26240
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe from_string method in python-pdfkit 1.0.0 allows arbitrary JavaScript execution within the server application context and enables exfiltration of local files. This is a code injection vulnerability in PDF generation where unsanitized input passed to from_string can be leveraged to execute commands and read sensitive files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify python-pdfkit installation and versionRun 'pip show python-pdfkit' or check your requirements.txt / pyproject.toml for 'python-pdfkit' versionAffected if The installed version is 1.0.0 or if no version is specified but the library is present
-
Locate from_string method usage in codeSearch your codebase for calls to 'pdfkit.from_string' using grep or IDE searchAffected if The from_string method is being called anywhere in your application
-
Inspect input handling to from_stringReview the code paths that feed data into from_string calls - check if user-supplied data flows directly to this method without sanitizationAffected if Unsvalidated or unsanitized user input is passed directly to from_string
-
Verify PDF generation environment isolationCheck whether PDF generation runs in a sandboxed process, container, or isolated environment with limited privilegesAffected if PDF generation runs with elevated privileges or without isolation from sensitive file systems
-
Review PDF generation logs for suspicious activityCheck application and system logs for unusual PDF generation patterns, especially involving from_string with unexpected contentAffected if Logs show unexpected or malicious PDF generation requests
You are affected if python-pdfkit 1.0.0 is installed and the from_string method is used with unsanitized input in your application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict or disable the from_string method, implement strict input validation and sanitization for all PDF generation inputs, run PDF generation in isolated sandboxed environments, and monitor for suspicious PDF generation patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26240 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26240 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data