Directory Traversal in featurebook

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Affected versions of featurebook resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system. The featurebook package is not intended to be run in production code nor to be exposed to an untrusted network. Proof of Concept Recommendation No direct patch is currently available. At this time, the best mitigation is to ensure that featurebook is not running in production or exposed to an untrusted network.

Published by the source

1 Sep 2020, 19:03 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7x92-2j68-h32c

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7x92-2j68-h32c

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

# Patch Next advisory brief: GHSA-7x92-2j68-h32c

Advisory: Directory Traversal in featurebook
IDs: GHSA-7x92-2j68-h32c
Record: https://patchnext.com/advisories/ghsa-7x92-2j68-h32c (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm featurebook: affected every version

## Suggested inspection (read-only)
- `npm ls featurebook --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on featurebook.
- 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://osv.dev/vulnerability/GHSA-7x92-2j68-h32c (OSV record GHSA-7x92-2j68-h32c lists affected ranges: npm featurebook >=0)
- Verified: https://github.com/advisories/GHSA-7x92-2j68-h32c (GitHub-reviewed advisory GHSA-7x92-2j68-h32c lists affected ranges: npm featurebook >=0)

Commands are suggestions: review each one before running it.