vulnerability / NVI-00010114 / Revision 5
Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root
GitHub lists this reviewed advisory for fallow, @fallow-cli/fallow-node, fallow-cli, fallow-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
3.3 low
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
3.3 LOW (3.1)
security-advisories@github.com severity; no combined Null risk score.
0.187%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08303. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
fallow
source listed>= 2.68.0, < 3.34.0
### 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 a
@fallow-cli/fallow-node
source listed>= 2.68.0, < 3.34.0
### 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 a
fallow-cli
source listed>= 2.68.0, < 3.34.0
### 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 a
fallow-core
source listed>= 2.68.0, < 3.34.0
### 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 a
fallow
source listedSEMVER: introduced 2.68.0; fixed 3.34.0
### 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 a
@fallow-cli/fallow-node
source listedSEMVER: introduced 2.68.0; fixed 3.34.0
### 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 a
fallow-cli
source listedSEMVER: introduced 2.68.0; fixed 3.34.0
### 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 a
fallow-core
source listedSEMVER: introduced 2.68.0; fixed 3.34.0
### 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 a
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
- vendor patch
The original advisory lists fixed boundaries 3.34.0 for fallow. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 3.34.0 for @fallow-cli/fallow-node. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-jfwm-3p3c-6hx5 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
- GHSA-jfwm-3p3c-6hx5 ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2026-115569 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2026-115569 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 5 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 4 ·
Source facts changed; compare the preserved prior revision.
- Revision 3 ·
Source facts changed; compare the preserved prior revision.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.