---
id: "CVE-2026-115569"
kind: "vulnerability"
aliases: ["CVE-2026-115569", "GHSA-jfwm-3p3c-6hx5"]
title: "Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root"
severity: "low"
cvss: 3.3
epss: 0.00178
exploited: false
status: "open"
category: "package"
products: [{"name": "fallow", "fixed": ["3.34.0"], "affected": ">= 2.68.0, < 3.34.0", "ecosystem": "npm"}, {"name": "@fallow-cli/fallow-node", "fixed": ["3.34.0"], "affected": ">= 2.68.0, < 3.34.0", "ecosystem": "npm"}, {"name": "fallow-cli", "fixed": ["3.34.0"], "affected": ">= 2.68.0, < 3.34.0", "ecosystem": "cargo"}, {"name": "fallow-core", "fixed": ["3.34.0"], "affected": ">= 2.68.0, < 3.34.0", "ecosystem": "cargo"}]
ecosystems: ["cargo", "npm"]
tags: ["ci", "coding-agents", "cwe-22", "cwe-59", "javascript", "jest", "npm", "package", "rust", "vitest"]
not_affected_if: ["no-projects-config", "trusted-repos-only"]
published_at: "2026-10-23T19:17:44+00:00"
first_seen_at: "2026-10-23T21:57:34+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115569", "first_seen_at": "2026-10-23T21:57:34+00:00"}, {"source": "ghsa", "url": "https://github.com/advisories/GHSA-jfwm-3p3c-6hx5", "first_seen_at": "2026-10-23T22:05:18+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-115569", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root

Fallow 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, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:fallow affected >= 2.68.0, < 3.34.0 fixed 3.34.0
- npm:@fallow-cli/fallow-node affected >= 2.68.0, < 3.34.0 fixed 3.34.0
- cargo:fallow-cli affected >= 2.68.0, < 3.34.0 fixed 3.34.0
- cargo:fallow-core affected >= 2.68.0, < 3.34.0 fixed 3.34.0

## How to check

- Check the installed version with `npx fallow --version` or `cargo tree -p fallow-cli`; versions from `2.68.0` up to but not including `3.34.0` are affected.
- Inspect `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.

## Fix

- Upgrade `fallow`, `@fallow-cli/fallow-node`, `fallow-cli` and `fallow-core` to `3.34.0`.
- Until upgraded, run Fallow only on repositories you trust.

## Timeline

- 2026-10-23T21:57:34+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115569
- 2026-10-23T22:05:18+00:00 ghsa https://github.com/advisories/GHSA-jfwm-3p3c-6hx5
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-115569

## From the sources

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

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_