{"items":[{"id":"NVI-00010114","kind":"vulnerability","title":"Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jfwm-3p3c-6hx5","CVE-2026-115569"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-257011762ae77564a503242d6d700552"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.34.0 for fallow. Confirm the publisher’s latest guidance.","source_ids":["sr-66da84abfb0763818e026425862e0560"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.34.0 for @fallow-cli/fallow-node. Confirm the publisher’s latest guidance.","source_ids":["sr-66da84abfb0763818e026425862e0560"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T21:57:38.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-17cd82475a49a56b5b6785cf0fc3ec70"},{"kind":"CVSS","as_of":"2026-10-30T20:17:01.853Z","value":"3.3 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-394a8a9c0d64db9499000243beab3412"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.187%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08303. Missing scores are unknown.","source_id":"sr-257011762ae77564a503242d6d700552"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-17cd82475a49a56b5b6785cf0fc3ec70","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-66da84abfb0763818e026425862e0560","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-04T09:59:53.096Z"},{"id":"sr-394a8a9c0d64db9499000243beab3412","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115569","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-115569","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:52.895Z"},{"id":"sr-257011762ae77564a503242d6d700552","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-115569","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.266Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]}],"null_published_at":"2026-11-06T15:18:11.415Z","source_updated_at":"2026-10-23T21:57:38.000Z","source_disclosed_at":"2026-10-23T21:57:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010114","kind":"vulnerability","title":"Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jfwm-3p3c-6hx5","CVE-2026-115569"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-866c930befe41549f94bad3d390300c9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.34.0 for fallow. Confirm the publisher’s latest guidance.","source_ids":["sr-66da84abfb0763818e026425862e0560"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.34.0 for @fallow-cli/fallow-node. Confirm the publisher’s latest guidance.","source_ids":["sr-66da84abfb0763818e026425862e0560"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T21:57:38.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-17cd82475a49a56b5b6785cf0fc3ec70"},{"kind":"CVSS","as_of":"2026-10-30T20:17:01.853Z","value":"3.3 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-394a8a9c0d64db9499000243beab3412"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.187%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08305. Missing scores are unknown.","source_id":"sr-866c930befe41549f94bad3d390300c9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-17cd82475a49a56b5b6785cf0fc3ec70","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-66da84abfb0763818e026425862e0560","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-04T09:59:53.096Z"},{"id":"sr-394a8a9c0d64db9499000243beab3412","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115569","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-115569","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:52.895Z"},{"id":"sr-866c930befe41549f94bad3d390300c9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-115569","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:20:46.853Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-66da84abfb0763818e026425862e0560"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":["SEMVER: introduced 2.68.0; fixed 3.34.0"]}],"null_published_at":"2026-11-05T03:52:54.736Z","source_updated_at":"2026-10-23T21:57:38.000Z","source_disclosed_at":"2026-10-23T21:57:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010114","kind":"vulnerability","title":"Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jfwm-3p3c-6hx5","CVE-2026-115569"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-866c930befe41549f94bad3d390300c9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T21:57:38.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-17cd82475a49a56b5b6785cf0fc3ec70"},{"kind":"CVSS","as_of":"2026-10-30T20:17:01.853Z","value":"3.3 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-394a8a9c0d64db9499000243beab3412"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.187%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08305. Missing scores are unknown.","source_id":"sr-866c930befe41549f94bad3d390300c9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-17cd82475a49a56b5b6785cf0fc3ec70","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-394a8a9c0d64db9499000243beab3412","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115569","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-115569","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:52.895Z"},{"id":"sr-866c930befe41549f94bad3d390300c9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-115569","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:20:46.853Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]}],"null_published_at":"2026-11-04T10:04:35.932Z","source_updated_at":"2026-10-23T21:57:38.000Z","source_disclosed_at":"2026-10-23T21:57:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010114","kind":"vulnerability","title":"Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jfwm-3p3c-6hx5","CVE-2026-115569"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-866c930befe41549f94bad3d390300c9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T21:57:38.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-17cd82475a49a56b5b6785cf0fc3ec70"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.187%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08305. Missing scores are unknown.","source_id":"sr-866c930befe41549f94bad3d390300c9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-17cd82475a49a56b5b6785cf0fc3ec70","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-866c930befe41549f94bad3d390300c9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-115569","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:20:46.853Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]}],"null_published_at":"2026-11-03T10:03:21.819Z","source_updated_at":"2026-10-23T21:57:38.000Z","source_disclosed_at":"2026-10-23T21:57:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010114","kind":"vulnerability","title":"Fallow: Jest and Vitest `projects` entries let an analyzed repository make Fallow read files outside the project root","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jfwm-3p3c-6hx5","CVE-2026-115569"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T21:57:38.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-17cd82475a49a56b5b6785cf0fc3ec70"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-17cd82475a49a56b5b6785cf0fc3ec70","url":"https://github.com/advisories/GHSA-jfwm-3p3c-6hx5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jfwm-3p3c-6hx5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"@fallow-cli/fallow-node","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-cli","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]},{"certainty":"source_listed","source_ids":["sr-17cd82475a49a56b5b6785cf0fc3ec70"],"technology":"fallow-core","known_exclusions":[],"conditions_summary":"### Impact\n\nFallow 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:\n\n- an absolute path or glob, for example `/etc/*`;\n- a path with `..` segments, for example `../*`;\n- a glob with a `.*` segment, because the `glob` crate also tests `..` against a segment that starts with a literal `.`;\n- a symlink in the project root to a directory above it;\n- the `extends` path of a Vitest inline project;\n- a script `--config` path that is a symlink to a file outside the project root.\n\nFallow 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.\n\nThe 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","public_affected_ranges":[">= 2.68.0, < 3.34.0"]}],"null_published_at":"2026-10-31T22:13:48.415Z","source_updated_at":"2026-10-23T21:57:38.000Z","source_disclosed_at":"2026-10-23T21:57:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:07:08.657Z"}],"next_cursor":null,"snapshot_revision":"42594"}