Skip to content

[agent] chore(deps): add override to bump tar-fs to >=2.1.4#706

Draft
github-actions[bot] wants to merge 1 commit intomainfrom
security/fix-tar-fs-cve-bc0b116581eefe29
Draft

[agent] chore(deps): add override to bump tar-fs to >=2.1.4#706
github-actions[bot] wants to merge 1 commit intomainfrom
security/fix-tar-fs-cve-bc0b116581eefe29

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Adds an npm overrides entry to the root package.json to ensure tar-fs resolves to >=2.1.4, fixing three high-severity path traversal / symlink vulnerabilities.

Vulnerabilities addressed

Alert Advisory CVE Severity Patched in
#66 GHSA-pq67-2wwv-3xjx CVE-2024-12905 High (7.5) 2.1.2
#68 GHSA-8cj5-5rvv-wf4v CVE-2025-48387 High (8.7) 2.1.3
#82 GHSA-vj76-c3g6-qr5v CVE-2025-59343 High (8.7) 2.1.4

All three are path traversal / symlink-following issues in tar-fs that allow a maliciously crafted tarball to write files outside the intended extraction directory.

Why overrides?

tar-fs is a transitive dependency pulled in by prebuild-install (which is used by kerberos and mongodb-client-encryption). prebuild-install@7.1.3 (latest) still declares tar-fs ^2.0.0, so bumping the direct dependency is not possible — there is no direct dependency on tar-fs in any workspace package.json. An npm overrides entry is therefore the correct mechanism to force resolution to a patched version.

The lockfile now resolves tar-fs to 3.1.2 (which satisfies >=2.1.4). npm audit reports no remaining tar-fs vulnerabilities.

Generated by Dependabot remediation agent · ● 889.7K ·

Adds npm override to ensure tar-fs resolves to >=2.1.4, fixing three
high-severity path traversal / symlink vulnerabilities:

- GHSA-pq67-2wwv-3xjx (CVE-2024-12905) – patched in 2.1.2
- GHSA-8cj5-5rvv-wf4v (CVE-2025-48387) – patched in 2.1.3
- GHSA-vj76-c3g6-qr5v (CVE-2025-59343) – patched in 2.1.4

tar-fs is a transitive dependency pulled in by prebuild-install (via
kerberos and mongodb-client-encryption). prebuild-install declares
'tar-fs ^2.0.0' but has not shipped a release that pins to >=2.1.4, so
an npm overrides entry is the appropriate fix.

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