Fallow Core
Monthly
Fallow 2.68.0 through 3.33.1, when run on an untrusted repository, can be induced to read Jest `projects` entries (and, from 3.33.1, Vitest `test.projects` entries, Vitest inline-project `extends` paths, and symlinked script `--config` paths) that resolve outside the project root via absolute paths, `..` segments, dot-prefixed wildcard globs, or in-root symlinks to parent directories. The outside files are parsed as test-runner configuration only to credit dependencies, setup files, and JSX import sources, so the attacker's payoff is altered unused-dependency and unused-file findings rather than disclosure of file contents - nothing is printed or sent over the network. Exploitation requires a user, CI job, or agent to execute Fallow against the hostile repository (AV:L, UI:R, unauthenticated per the CVSS vector), and no public exploit code was identified at time of analysis; priority signals are consistent with low, non-urgent risk and monitoring.
Fallow 2.68.0 through 3.33.1, when run on an untrusted repository, can be induced to read Jest `projects` entries (and, from 3.33.1, Vitest `test.projects` entries, Vitest inline-project `extends` paths, and symlinked script `--config` paths) that resolve outside the project root via absolute paths, `..` segments, dot-prefixed wildcard globs, or in-root symlinks to parent directories. The outside files are parsed as test-runner configuration only to credit dependencies, setup files, and JSX import sources, so the attacker's payoff is altered unused-dependency and unused-file findings rather than disclosure of file contents - nothing is printed or sent over the network. Exploitation requires a user, CI job, or agent to execute Fallow against the hostile repository (AV:L, UI:R, unauthenticated per the CVSS vector), and no public exploit code was identified at time of analysis; priority signals are consistent with low, non-urgent risk and monitoring.