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


- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-jfwm-3p3c-6hx5

## What is CVE-2026-115569?

CVE-2026-115569 is a low-severity vulnerability in @fallow-cli fallow, published on 23 Oct 2026. 

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-115569?

8 open source packages ship an affected version, including @fallow-cli/fallow-node, fallow-cli and fallow-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@fallow-cli/fallow-node` | npm | From 2.68.0 | 3.34.0 |
| `@fallow-cli/fallow-node` | npm | From 2.68.0 | 3.34.0 |
| `fallow-cli` | crates.io | From 2.68.0 | 3.34.0 |
| `fallow-cli` | crates.io | From 2.68.0 | 3.34.0 |
| `fallow-core` | crates.io | From 2.68.0 | 3.34.0 |
| `fallow-core` | crates.io | From 2.68.0 | 3.34.0 |
| `fallow` | npm | From 2.68.0 | 3.34.0 |
| `fallow` | npm | From 2.68.0 | 3.34.0 |

## How do I fix CVE-2026-115569?

Upgrade @fallow-cli/fallow-node to 3.34.0 or later.

## Is CVE-2026-115569 being exploited?

There is no known exploitation of CVE-2026-115569 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115569 and fix it if it is affected.

What it is: CVE-2026-115569 is a low-severity vulnerability in @fallow-cli fallow, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115569 in the wild and no public exploit code.

Affected packages and fixed versions:
- @fallow-cli/fallow-node (npm): affected from 2.68.0; fixed in 3.34.0
- @fallow-cli/fallow-node (npm): affected from 2.68.0; fixed in 3.34.0
- fallow-cli (crates.io): affected from 2.68.0; fixed in 3.34.0
- fallow-cli (crates.io): affected from 2.68.0; fixed in 3.34.0
- fallow-core (crates.io): affected from 2.68.0; fixed in 3.34.0
- fallow-core (crates.io): affected from 2.68.0; fixed in 3.34.0
- fallow (npm): affected from 2.68.0; fixed in 3.34.0
- fallow (npm): affected from 2.68.0; fixed in 3.34.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115569/ (Markdown: https://insights.sbomify.com/CVE-2026-115569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115569
- OSV: https://osv.dev/vulnerability/CVE-2026-115569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115569/
Summaries are generated and may contain mistakes; the official description above is the record.