Fix possible fix(deps): 9 vulnerable dependencies in pnpm-lock.yaml - #1136
Open
begininvoke wants to merge 1 commit into
Open
Fix possible fix(deps): 9 vulnerable dependencies in pnpm-lock.yaml#1136begininvoke wants to merge 1 commit into
begininvoke wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposing a fix for something flagged in
pnpm-lock.yaml. It is around line 1.The node-tar library (<=7.5.2) fails to sanitize the linkpath of Hardlink and Symlink entries when preservePaths is false (default). This allows an attacker to craft a malicious archive that bypasses extraction root restrictions, leading to arbitrary file overwrite via hardlinks and symlink poisoning via absolute symlink targets. The vulnerability is HIGH severity, enabling potential remote code execution or system file corruption.
Updated tar version to 7.5.21 in specifiers and dependencies to resolve 9 CVEs.
For reference: rule
CVE-2026-23745. Rated high.I may well be missing context here — if the current code is deliberate, feel free to close this.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.