CVE-2026-115569 json
Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root
published 17d ago modified 10d ago also GHSA-jfwm-3p3c-6hx5 , EUVD-2026-109119
- cvss
- 3.3
- 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 8%
- public exploits
- 0
- none known
Summary
Fallow is a codebase intelligence tool for TypeScript and JavaScript. From 2.68.0 until 3.34.0, Fallow follows attacker-controlled Jest projects paths outside the project root through absolute paths, parent segments, dot-prefixed wildcard globs, or symlinks. In version 3.33.1, the same behavior also affects Vitest test.projects paths, Vitest inline-project extends paths, and symlinked script --config paths. Fallow parses the outside files as test-runner configuration and uses them to credit dependencies, setup files, and JSX import sources, which can change unused dependency and unused file findings in CI or agent analysis. The outside file contents are not printed or sent over the network. This issue is fixed in version 3.34.0.
Patch / fix
- npm fallow 3.34.0
- npm @fallow-cli/fallow-node 3.34.0
- crates.io fallow-cli 3.34.0
- crates.io fallow-core 3.34.0
- github.com/fallow-rs/fallow@75c0c60 commit
- github.com/fallow-rs/fallow#3556 pull request
- github.com/fallow-rs/fallow/releases/tag/v3.34.0 release
Is CVE-2026-115569 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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | fallow | >=2.68.0, <3.34.0 |
3.34.0 |
| npm | @fallow-cli/fallow-node | >=2.68.0, <3.34.0 |
3.34.0 |
| crates.io | fallow-cli | >=2.68.0, <3.34.0 |
3.34.0 |
| crates.io | fallow-core | >=2.68.0, <3.34.0 |
3.34.0 |
Affected products
- fallow-rs fallow
- @fallow-cli fallow-node
- fallow-rs fallow-cli
- fallow-rs fallow-core
Classification
References
-
github.com
/fallow-rs/fallow/pull/3556
web
-
github.com
/fallow-rs/fallow/commit/75c0c60948a53ddfe042e65b446343989f4c5649
web
-
github.com
/fallow-rs/fallow/security/advisories/GHSA-jfwm-3p3c-6hx5
web
-
github.com
/fallow-rs/fallow/releases/tag/v3.34.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-115569
advisory
-
github.com
/fallow-rs/fallow
package
Sources
- CVE List CVE-2026-115569
- GitHub Advisory GHSA-jfwm-3p3c-6hx5
- NVD CVE-2026-115569
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.