Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-jfwm-3p3c-6hx5

LowCVSS 3.3 / 10
Published Oct 23, 2026·Last modified Oct 23, 2026
Affected Components(4)
crates.io logofallow-cli
2.68.0 – 3.34.0
crates.io logofallow-core
2.68.0 – 3.34.0
npm logofallow
2.68.0 – 3.34.0
1 / 2
Description

Impact

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 ../*;
  • a glob with a .* segment, because the glob crate also tests .. against a segment that starts with a literal .;
  • a symlink in the project root to a directory above it;
  • the extends path of a Vitest inline project;
  • a script --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.

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 <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.

Workarounds

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.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
3.3

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.

Threat Intelligence
3.1

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.19%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard