Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.3amended

Fallow: A .* glob segment let an analyzed repository make Fallow test paths in the parent of the project root

GHSA-h4fr-cmh5-qr62

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@fallow-cli/fallow-node 3.34.0; fallow 3.34.0; fallow-cli 3.34.0; fallow-core 3.34.0; fallow-config 3.34.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-h4fr-cmh5-qr62

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-h4fr-cmh5-qr62

  3. Revision 2 · amended ·

    Amended from osv record GHSA-h4fr-cmh5-qr62

  4. Revision 1 · created ·

    Published from ghsa record GHSA-h4fr-cmh5-qr62

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-h4fr-cmh5-qr62

Advisory: Fallow: A `.*` glob segment let an analyzed repository make Fallow test paths in the parent of the project root
IDs: GHSA-h4fr-cmh5-qr62
Record: https://patchnext.com/advisories/ghsa-h4fr-cmh5-qr62 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @fallow-cli/fallow-node 3.34.0; fallow 3.34.0; fallow-cli 3.34.0; fallow-core 3.34.0; fallow-config 3.34.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @fallow-cli/fallow-node: affected < 3.34.0; fixed in 3.34.0
- npm fallow: affected < 3.34.0; fixed in 3.34.0
- crates.io fallow-cli: affected < 3.34.0; fixed in 3.34.0
- crates.io fallow-core: affected < 3.34.0; fixed in 3.34.0
- crates.io fallow-config: affected < 3.34.0; fixed in 3.34.0

## Suggested inspection (read-only)
- `npm ls @fallow-cli/fallow-node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls fallow --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- crates.io fallow-cli: check the installed version with your package manager.
- crates.io fallow-core: check the installed version with your package manager.
- crates.io fallow-config: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @fallow-cli/fallow-node, fallow, fallow-cli, fallow-core, fallow-config.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h4fr-cmh5-qr62 (GitHub-reviewed advisory GHSA-h4fr-cmh5-qr62 lists affected ranges: npm fallow >=0 =0 <3.34.0)
- Verified: https://osv.dev/vulnerability/GHSA-h4fr-cmh5-qr62 (OSV record GHSA-h4fr-cmh5-qr62 lists affected ranges: npm fallow >=0 =0 =0 =0 =0 <3.34.0 (fixed))
- Verified: https://github.com/advisories/GHSA-h4fr-cmh5-qr62 (GitHub-reviewed advisory GHSA-h4fr-cmh5-qr62 lists affected ranges: npm fallow >=0 =0 =0 =0 =0 <3.34.0)

Commands are suggestions: review each one before running it.

Loading voting…