Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.55% for the current model date.
BlackTreeCVE Intelligencemafintosh · tar-fs
Official source article: GitHub GHSA-VJ76-C3G6-QR5V ↗. Check the applicable product and release in the original source.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | node-tar-fs | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9+~cs2.0.4-1+deb13u1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | node-tar-fs | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.1.3-0+deb12u2 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | node-tar-fs | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9+~cs2.0.4-2 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | node-tar-fs | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9+~cs2.0.4-2 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | node-tar-fs | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 2.1.1-6ubuntu0.24.04.1~esm1 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmtar-fs | >= 3.0.0, < 3.1.1 | 3.1.1 | GitHub advisory ↗upstream repository advisory · 3 Nov 2025 |
| npmtar-fs | >= 2.0.0, < 2.1.4 | 2.1.4 | GitHub advisory ↗upstream repository advisory · 3 Nov 2025 |
| npmtar-fs | < 1.16.6 | 1.16.6 | GitHub advisory ↗upstream repository advisory · 3 Nov 2025 |
| npmtar-fs | SEMVER: introduced 3.0.0; fixed 3.1.1 | 3.1.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmtar-fs | SEMVER: introduced 2.0.0; fixed 2.1.4 | 2.1.4 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmtar-fs | SEMVER: introduced 0; fixed 1.16.6 | 1.16.6 | OSV record ↗aggregator derived · 10 Sep 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availabletar-fs provides filesystem bindings for tar-stream. Versions prior to 3.1.1, 2.1.3, and 1.16.5 are vulnerable to symlink validation bypass if the destination directory is predictable with a specific tarball. This issue has been patched in version 3.1.1, 2.1.4, and 1.16.6. A workaround involves using the ignore option on non files/directories.
tar-fs provides filesystem bindings for tar-stream. Versions prior to 3.1.1, 2.1.3, and 1.16.5 are vulnerable to symlink validation bypass if the destination directory is predictable with a specific tarball. This issue has been patched in version 3.1.1, 2.1.4, and 1.16.6. A workaround involves using the ignore option on non files/directories.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
tar-fs provides filesystem bindings for tar-stream. Versions prior to 3.1.1, 2.1.3, and 1.16.5 are vulnerable to symlink validation bypass if the destination directory is predictable with a specific tarball. This issue has been patched in version 3.1.1, 2.1.4, and 1.16.6. A workaround involves using the ignore option on non files/directories.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Published 24 Sept 2025 · Last source change 3 Nov 2025, 18:13 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Core structured fields are present and their contributing authorities are shown above.