Repository navigation
fix(deps): Patch critical tar archive vulnerability - #157
Merged
Merged
Conversation
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
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.
CI dependency installation fails because Aegis rejects
tar@7.5.16withcriticalCVE, as seen in PR #156's failed install. The installed version is affected by CVE-2026-59873 / GHSA-23hp-3jrh-7fpw, which permits resource exhaustion while extracting archives.Pin the transitive tar dependency to 7.5.22 and regenerate the lockfile. This version also covers the newer GHSA-r292-9mhp-454m fix. The dependency comes from the development-only
@yao-pkg/pkgpackager, which uses tar to extract downloaded Node.js archives. Include a non-release changelog entry for this toolchain update.This PR targets main independently of #156; merge this first, then update that PR from main. Existing security enforcement is unchanged.
Validation:
Prompted by: @sds