Impact
Applications using the Node.js bundles of jspdf version 3.0.4 or earlier can expose local files when an untrusted path reaches jsPDF file loading. The affected APIs are loadFile, addImage, html, and addFont; referenced file contents can be included in a generated PDF. Browser builds are not affected [S1] [S2]. The upstream vendor and reviewed GitHub advisory score the issue 9.2 Critical under CVSS v4, while NVD separately scores it 7.5 High under CVSS v3.1 [S1] [S2] [S5].
Root Cause
In affected Node.js bundles, file-loading paths could reach local filesystem reads without a deny-by-default filesystem policy. Exploitation still requires application-specific data flow: an untrusted path must reach one of the affected APIs. The upstream fix restricts filesystem access by default, and jsPDF 4.0.0 contains that change [S1] [S3] [S4].
How FixVibe covers it
FixVibe's GitHub repository scans flag jspdf versions up to and including 3.0.4 in package manifests and lockfiles, rated High, with the file and version so you can upgrade to 4.0.0.
Remediation
Upgrade jspdf to 4.0.0 or later, regenerate the lockfile, rebuild the application, and verify that the resolved production dependency is no longer 3.0.4 or earlier [S1] [S4]. Review every use of loadFile, addImage, html, and addFont so untrusted input cannot select filesystem paths. For Node.js deployments, use the Node permission model where supported and enforce narrow canonical-path allowlists for any required file access; do not rely on removing traversal strings alone. Validate the fix with unit and integration tests using approved fixture paths rather than reproducing access to sensitive files [S1] [S3].
