Skip to content

[agent] chore(deps): bump tar to >=7.5.16 (GHSA-vmf3-w455-68vh)#793

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/bump-tar-7.5.16-017af69d0e70e696
Draft

[agent] chore(deps): bump tar to >=7.5.16 (GHSA-vmf3-w455-68vh)#793
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/bump-tar-7.5.16-017af69d0e70e696

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Security fix: tar PAX size override interpretation differential

Resolves Dependabot alert #279.

Advisory

  • GHSA-vmf3-w455-68vh / CVE-2026-53655 (medium, CVSS 4.0: 6.9)
  • tar (node-tar) ≤ 7.5.15 applies PAX extended-header size= overrides to intermediary GNU long-name (L) / long-link (K) headers, causing a parser interpretation differential (CWE-436). A crafted archive can present different member lists to node-tar vs. GNU tar/libarchive/Python tarfile, defeating security scanners. Fixed in tar@7.5.16.

Changes

  1. packages/mongodb-downloader/package.json — bumped the direct tar dependency from ^7.5.11^7.5.16.
  2. package.json (root) — added overrides.tar >= 7.5.16.

Why the override? lerna@9.0.7 (a root devDependency) pins tar to exactly 7.5.11 in its own dependency tree and 9.0.7 is the latest lerna release — there is no lerna upgrade that clears the advisory. The overrides entry forces every tar consumer in the workspace to resolve to the patched 7.5.16, consolidating what would otherwise have been a nested installation into a single root-level entry.

Generated by Dependabot remediation agent · ● 1M ·

- Bump direct dependency tar in packages/mongodb-downloader from ^7.5.11 to ^7.5.16
- Add overrides.tar >= 7.5.16 in root package.json to force all transitive
  consumers (lerna pins tar@7.5.11 exactly) to use the patched version

Fixes Dependabot alert #279 (CVE-2026-53655 / GHSA-vmf3-w455-68vh).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants