CVE-2026-24909 json
vlt Mishandles Path Sanitization for tar
published 9mo ago modified 4mo ago also GHSA-gf2c-jwcj-x929 , EUVD-2026-4860
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
vlt before 1.0.0-rc.10 mishandles path sanitization for tar, leading to path traversal during extraction.
Patch / fix
- npm @vltpkg/tar 1.0.0-rc.10
- vlt vlt 1.0.0-rc.10
- github.com/vltpkg/vltpkg@ff8d409 commit
- github.com/vltpkg/vltpkg#1334 pull request
- github.com/vltpkg/vltpkg/releases/tag/v1.0.0-rc.10 release
Is CVE-2026-24909 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @vltpkg/tar | <1.0.0-rc.10 |
1.0.0-rc.10 |
Affected products
- vlt vlt
Classification
- Weakness
-
- CWE-23 Relative Path Traversal
References
-
github.com
/vltpkg/vltpkg/pull/1334
web
-
github.com
/vltpkg/vltpkg/commit/ff8d4099a1929772cea2adf131285e90ede6b0dd
web
-
scworld.com
/news/six-javascript-zero-day-bugs-lead-to-fears-of-supply-chain-attack
web
-
github.com
/vltpkg/vltpkg/releases/tag/v1.0.0-rc.10
web
-
koi.ai
/blog/packagegate-6-zero-days-in-js-package-managers-but-npm-wont-act
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-24909
advisory
-
github.com
/vltpkg/vltpkg
package
Sources
- CVE List CVE-2026-24909
- GitHub Advisory GHSA-gf2c-jwcj-x929
- NVD CVE-2026-24909
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.