Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
Fallow can reveal files outside project root
published 29 days ago
Summary
The Fallow tool may let a malicious repository discover whether files or folders exist one level above the project directory. This can expose the structure of your build environment when the tool’s output is shown in logs or pull‑request comments. Update Fallow to version 3.34.0 or later to block this behavior.
What to do
- Update GitHub Actions fallow to version 3.34.0.
- Update fallow-cli @fallow-cli/fallow-node to version 3.34.0.
- Update bartwaardenburg fallow-cli to version 3.34.0.
- Update bartwaardenburg fallow-config to version 3.34.0.
- Update bartwaardenburg fallow-core to version 3.34.0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| npm | GitHub Actions | fallow |
< 3.34.0 Fix: upgrade to 3.34.0
|
| npm | fallow-cli | @fallow-cli/fallow-node |
< 3.34.0 Fix: upgrade to 3.34.0
|
| crates.io | bartwaardenburg | fallow-cli |
< 3.34.0 Fix: upgrade to 3.34.0
|
| crates.io | bartwaardenburg | fallow-config |
< 3.34.0 Fix: upgrade to 3.34.0
|
| crates.io | bartwaardenburg | fallow-core |
< 3.34.0 Fix: upgrade to 3.34.0
|
Original advisory text
Fallow: A `.*` glob segment let an analyzed repository make Fallow test paths in the parent of the project root
### Impact
Fallow expands some globs from the analyzed repository on disk. Before 3.34.0, a segment such as `.*`, `.?` or `..*` in such a glob also matched the special `..` entry. The `glob` crate tests `..` against a segment that starts with a literal `.`. Fallow validates plugin glob patterns and refuses absolute paths and `..` segments, but these segments passed that validation.
The attacker controls the repository content. The attacker must also be able to read the Fallow output, for example a CI log or a pull request comment. Then the attacker can learn if a file or directory exists in the parent of the project root:
- A plugin `fileExists` detection pattern such as `.*/marker.json` made the plugin active when `marker.json` existed in the parent directory.
- An external plugin `configPatterns` or `alwaysUsed` pattern could match a config file in the parent directory. When the plugin was active and declared `toolingDependencies`, the tooling detection credited the related dev dependency. An unused dependency finding could then disappear, and `--trace-dependency` printed the outside path.
- `fallow plugin-check` reported `path_exists: true` for a seeded entry that matched only in the parent directory.
Fallow tested only that these paths exist. It did not read or print the content of a file outside the project root through these globs.
The Jest, Vitest and Rstest project globs had the same `.*` problem, and the Jest and Vitest ones also read file content. GHSA-jfwm-3p3c-6hx5 describes that case.
### Patches
Fixed in 3.34.0. Fallow now rewrites a leading `.` in a wildcard segment to `[.]` before it expands the glob on disk. `[.]` matches the same hidden files and directories inside the project root. The `glob` crate does not test `..` against it.
### Workarounds
Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the `detection`, `configPatterns` and `alwaysUsed` patterns of its plugin files.
Fallow expands some globs from the analyzed repository on disk. Before 3.34.0, a segment such as `.*`, `.?` or `..*` in such a glob also matched the special `..` entry. The `glob` crate tests `..` against a segment that starts with a literal `.`. Fallow validates plugin glob patterns and refuses absolute paths and `..` segments, but these segments passed that validation.
The attacker controls the repository content. The attacker must also be able to read the Fallow output, for example a CI log or a pull request comment. Then the attacker can learn if a file or directory exists in the parent of the project root:
- A plugin `fileExists` detection pattern such as `.*/marker.json` made the plugin active when `marker.json` existed in the parent directory.
- An external plugin `configPatterns` or `alwaysUsed` pattern could match a config file in the parent directory. When the plugin was active and declared `toolingDependencies`, the tooling detection credited the related dev dependency. An unused dependency finding could then disappear, and `--trace-dependency` printed the outside path.
- `fallow plugin-check` reported `path_exists: true` for a seeded entry that matched only in the parent directory.
Fallow tested only that these paths exist. It did not read or print the content of a file outside the project root through these globs.
The Jest, Vitest and Rstest project globs had the same `.*` problem, and the Jest and Vitest ones also read file content. GHSA-jfwm-3p3c-6hx5 describes that case.
### Patches
Fixed in 3.34.0. Fallow now rewrites a leading `.` in a wildcard segment to `[.]` before it expands the glob on disk. `[.]` matches the same hidden files and directories inside the project root. The `glob` crate does not test `..` against it.
### Workarounds
Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the `detection`, `configPatterns` and `alwaysUsed` patterns of its plugin files.
References
- https://github.com/fallow-rs/fallow/security/advisories/GHSA-h4fr-cmh5-qr62 URL
- https://github.com/fallow-rs/fallow/pull/3548 URL
- https://github.com/fallow-rs/fallow/commit/133d4c862c74f4b1f0a7417c65b7157c11442... URL
- https://github.com/fallow-rs/fallow Product
- https://github.com/fallow-rs/fallow/releases/tag/v3.34.0 URL
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Type
CWE-22Path Traversal
Timeline
Published23 Oct 2026
Updated23 Oct 2026
First seen23 Oct 2026
Sources
GHSA-h4fr-cmh5-qr62 · OSV
Track software like this
Free during beta