Security research · CVE-2026-115569
Fallow: Jest and Vitest entries let an analyzed repository make Fallow read files outside the project root
Published Oct 23, 2026 · catalog updated Oct 23, 2026 · Fallow: Jest and Vitest
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-115569. EPSS is 0.19%. Act only if a listed version of Fallow: Jest and Vitest is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Fallow: Jest and Vitest).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low3.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.19%
- Remediation
- Version ranges on file
- Affected products
- cargo fallow-cli · cargo fallow-core · crates.io fallow-cli · crates.io fallow-core · npm @fallow-cli · npm @fallow-cli/fallow-node
### Impact Fallow reads the Jest and Vitest configs of the repository that it analyzes. A Jest entry or a Vitest entry can name a path. Fallow followed such an entry to a config file and read that file, also when the file was outside the project root. These forms reached outside the root: - an absolute path or glob, for example ; - a path with segments, for example ; - a glob with a segment, because the crate also tests against a segment that starts with a literal ; - a symlink in the project root to a directory above it; - the path of a Vitest inline project; - a script path that is a symlink to a file outside the project root. Fallow parsed each of these files as a test runner config. Fallow used the content only to credit dependencies, setup files and JSX import sources. Thus unused dependency and unused file findings could change. Fallow did not print the content or send it over the network. The Fallow threat model states that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content. Versions 2.68.0 to 3.33.1 read outside files through Jest . Version 3.33.1 also read them through Vitest . ### Patches Fixed in 3.34.0. Fallow now resolves each match with symlinks and segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as still works, also from the config of a workspace package. Fallow also does not read a script path that is a symlink to a file outside the project root. ### Workarounds Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the entries of its and files.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cargo fallow-cliversion unspecified
- cargo fallow-coreversion unspecified
- crates.io fallow-cli2.68.0 → 3.34.0
- crates.io fallow-core2.68.0 → 3.34.0
- npm @fallow-cliversion unspecified
- npm @fallow-cli/fallow-node2.68.0 → 3.34.0
- npm @fallow-cli/fallow-node>= 2.68.0, < 3.34.0
- npm fallow2.68.0 → 3.34.0
- npm fallow>= 2.68.0, < 3.34.0
- rust fallow-cli>= 2.68.0, < 3.34.0
- rust fallow-core>= 2.68.0, < 3.34.0
How to fix CVE-2026-115569
Upgrade
CVE-2026-115569 lists a fix boundary at 3.34.0. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.34.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-115569. EPSS is 0.19%. Act only if a listed version of Fallow: Jest and Vitest is installed.
Which versions are affected?
Compare what you have installed with 2.68.0 → 3.34.0, >= 2.68.0, < 3.34.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-22: Path Traversal; CWE-59: Link Following. EPSS 0.19%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · GitHub Advisory Database
Detected
### Impact Fallow reads the Jest and Vitest configs of the repository that it analyzes. A Jest entry or a Vitest entry can name a path. Fallow followed such an entry to a config file and read that file, also when the file was outside the project root. These forms reached outside the root: - an absolute path or glob, for example ; - a path with segments, for example ; - a glob with a segment, becau
Oct 23, 2026 · GitHub Advisory Database
Fix available
fallow fixed in 3.34.0; @fallow-cli/fallow-node fixed in 3.34.0; fallow-cli fixed in 3.34.0; fallow-core fixed in 3.34.0
Oct 23, 2026 · GitHub Advisory Database
Fix available
fallow fixed in 3.34.0
Oct 23, 2026 · GitHub Advisory Database
Fix available
@fallow-cli/fallow-node fixed in 3.34.0
Oct 23, 2026 · GitHub Advisory Database
Fix available
fallow-cli fixed in 3.34.0
Oct 23, 2026 · GitHub Advisory Database
Fix available
fallow-core fixed in 3.34.0
Oct 23, 2026 · GitHub Advisory Database
Updated
### Impact Fallow reads the Jest and Vitest configs of the repository that it analyzes. A Jest entry or a Vitest entry can name a path. Fallow followed such an entry to a config file and read that file, also when the file was outside the project root. These forms reached outside the root: - an absolute path or glob, for example ; - a path with segments, for example ; - a glob with a segment, becau
Sources
- CVE.orgVulnerability recordCVE-2026-115569
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-115569
30-day exploitation probability 0.19%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-jfwm-3p3c-6hx5
Fallow: Jest and Vitest entries let an analyzed repository make Fallow read files outside the project root
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-115569
Fallow reads the Jest and Vitest configs of the repository that it analyzes. A Jest projects entry or a Vitest test.projects entry can name a path. Fallow followed such an entry to a config file and read that file, also when the file was outside the project root. These forms reached outside the root: an absolute path or glob, for example /etc/ ; a path with .. segments, for example ../ ; …
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-jfwm-3p3c-6hx5
Fallow: Jest and Vitest entries let an analyzed repository make Fallow read files outside the project root
osv.dev
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 6, 2026
- GitLab Advisory DatabaseOct 27, 2026
- CVE.orgOct 24, 2026
- GitHub Advisory DatabaseOct 24, 2026
- OpenSSF OSV / OSV ScannerOct 24, 2026