CVE-2026-24909 is a medium-severity (CVSS 5.9) CWE-23 vulnerability in @vltpkg/tar. A fix is available for @vltpkg/tar — see the affected versions and patch details below.
vlt Mishandles Path Sanitization for tar
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-24909.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@vltpkg/tarnpmDescription
vlt before 1.0.0-rc.10 mishandles path sanitization for tar, leading to path traversal during extraction.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @vltpkg/tar | all versions | 1.0.0-rc.10npm install @vltpkg/tar@1.0.0-rc.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vltpkg/tar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vltpkg/tar to 1.0.0-rc.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-24909 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-24909 in your dependencies?
Find it across npm, including transitive dependencies.