Live › vulnerability › CVE-2026-115569
Go to dashboardFallow follows Jest `projects` and Vitest `test.projects` entries in an analyzed repository and parses files outside the project root as test runner configs. An attacker who supplies a crafted repository changes Fallow's unused dependency and unused file findings, but the file contents are not printed or sent over the network.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that run Fallow on repositories they did not write, such as CI jobs analyzing cloned or external code, or coding agents that run Fallow on untrusted repositories. Projects that only analyze their own code and use default Jest or Vitest config without out-of-root entries have little exposure.
projects| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| fallow | npm | >= 2.68.0, < 3.34.0 | 3.34.0 |
| @fallow-cli/fallow-node | npm | >= 2.68.0, < 3.34.0 | 3.34.0 |
| fallow-cli | cargo | >= 2.68.0, < 3.34.0 | 3.34.0 |
| fallow-core | cargo | >= 2.68.0, < 3.34.0 | 3.34.0 |
npx fallow --version or cargo tree -p fallow-cli; versions from 2.68.0 up to but not including 3.34.0 are affected.projects entries in jest.config.* and vitest.config.* of any repository you analyze for absolute paths, .. segments, .* glob segments, or symlinks pointing outside the root.fallow, @fallow-cli/fallow-node, fallow-cli and fallow-core to 3.34.0.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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:
/etc/*;.. segments, for example ../*;.* segment, because the glob crate also tests .. against a segment that starts with a literal .;extends path of a Vitest inline project;--config 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 projects. Version 3.33.1 also read them through Vitest test.projects.
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 <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.
Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.
This page as .md · .json · in your agent: get_signal("CVE-2026-115569")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.