fix(security): update jspdf to 4.0.0 to address CVE-2025-68428 #37553
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates jspdf from 3.0.4 to 4.0.0 to fix a critical Local File Inclusion/Path Traversal vulnerability (CVE-2025-68428). Reference: GHSA-f8cm-6447-x5h2
Contributor
|
Bito Automatic Review Skipped - Files Excluded |
3 tasks
Contributor
|
hi @Nancy-Chauhan, thanks for opening the PR. Can you post an after and before screenshot to see if PDF export functionalities are still intact? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates the transitive dependency
jspdffrom^3.0.2to^4.0.0to fix a critical security vulnerability.CVE-2025-68428: Local File Inclusion/Path Traversal vulnerability in jsPDF that could allow arbitrary file reads in Node.js environments.
Changes
jspdfversion constraint insuperset-frontend/package.jsonfrom^3.0.2to^4.0.0Impact Assessment
Low risk of breakage:
dom-to-pdffor browser-based PDF exportdownloadAsPdf.ts) should continue working without modificationSecurity Advisory
Test Plan
npm auditto confirm vulnerability is resolved