CVE-2025-68428

Home/CVE/jsPDF is a library to generate PDFs in JavaScript. Prior to version 4.0.0, user control of the first argument of the loa

CVE

jsPDF is a library to generate PDFs in JavaScript. Prior to version 4.0.0, user control of the first argument of the loa

jsPDF is a library to generate PDFs in JavaScript. Prior to version 4.0.0, user control of the first argument of the loadFile method in the node.js build allows local file inclusion/path traversal. If given the possibility to pass unsanitized paths to the loadFile method, a user can retrieve file contents of arbitrary files in the local file system the node process is running in.

The file contents are included verbatim in the generated PDFs. Other affected methods are addImage, html, and addFont. Only the node.js builds of the library are affected, namely the dist/jspdf.node.js and dist/jspdf.node.min.js files.

The vulnerability has been fixed in [email protected]. This version restricts file system access per default. This semver-major update does not introduce other breaking changes.

Some workarounds areavailable. With recent node versions, jsPDF recommends using the --permission flag in production. The feature was introduced experimentally in v20.0.0 and is stable since v22.13.0/v23.5.0/v24.0.0.

For older node versions, sanitize user-provided paths before passing them to jsPDF.

HIGH · CVSS 7.5 EPSS 0.0003

Act now

Public exploit or PoC is available
SSVC automatable: yes - attacks can be scripted at scale
CVSS base score ≥ 7.0

Sigma rules0 YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Vulners Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2025-68428, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

View attack path from CVE-2025-68428

◆

ATT&CK techniques

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

T1027 · Obfuscated Files or Information T1562.003 · Impair Command History Logging T1574.006 · Dynamic Linker Hijacking T1574.007 · Path Interception by PATH Environment Variable

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-126 · Path Traversal CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-267 · Leverage Alternate Encoding CAPEC-CAPEC-64 · Using Slashes and URL Encoding Combined to Bypass Validation Logic CAPEC-CAPEC-72 · URL Encoding CAPEC-CAPEC-76 · Manipulating Web Input to File System Calls CAPEC-CAPEC-78 · Using Escaped Slashes in Alternate Encoding CAPEC-CAPEC-79 · Using Slashes in Alternate Encoding CAPEC-CAPEC-80 · Using UTF-8 Encoding to Bypass Validation Logic

⬡

Weakness Classification

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CWE-35Path Traversal: '.../...//'
CWE-73External Control of File Name or Path

▤

Affected Products & Versions

parall jspdf< 4.0.0

▤

Affected Packages

Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.

npm jspdf CRITICAL fixed in 4.0.0

⚠

Public Exploits & PoCs

These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.

poc12nio/CVE-2025-68428_PoC (nomi-sec)

pocNurjaman2004/jsPDF-Bulk-Detector-CVE-2025-68428- (nomi-sec)

◈

Detection Rules (IDS/IPS)

et-openET WEB_SPECIFIC_APPS jsPDF Arbitrary File Read via Path Traversal PDF File Outbound (CVE-2025-68428)web-application-attack

Open rulesets (ET Open, Snort Community, abuse.ch) link to source. Commercial rulesets are reference-only.

▣

Scoring & Timeline

7.5

HIGH · CVSS v3.1 · [email protected]

View on NVD

Attack Vector

Network Adjacent Local Physical

Attack Complexity

Low High

Privileges Required

None Low High

User Interaction

None Required

Scope

Unchanged Changed

Confidentiality

None Low High

Integrity

None Low High

Availability

None Low High

Published to NVD05 Jan 2026 · 10:15 PM

CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

SSVC triage · cisa-vulnrichment

Exploitation

none

Automatable

yes

Technical impact

partial

SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.

⚑

Vendor Advisories

rhsaRHSA-2026:2568Important
rhsaRHSA-2026:2350Important
rhsaRHSA-2026:1517Important

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://github.com/parallax/jsPDF/commit/a688c8f479929b24a6543b1fa2d6364abb03066dPatch

https://github.com/parallax/jsPDF/releases/tag/v4.0.0ProductRelease Notes

https://github.com/parallax/jsPDF/security/advisories/GHSA-f8cm-6447-x5h2Third Party Advisory