Exposure of home directory through shescape on Unix with Bash

Exploitation

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

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-24725: 0.50% estimated exploitation activity in the next 30 days; percentile 42.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The issue allows for exposure of the home directory on Unix systems when using Bash with the escape or escapeAll functions from the shescape API with the interpolation option set to true. Other tested shells, Dash and Zsh, are not affected. Depending on how the output of shescape is used, directory traversal may be possible in the application using shescape. Patches The issue was patched in v1.5.1. Workarounds Manually escape all instances of the tilde character (~) using arg.replace(/~/g, "\\~"). References See GitHub issue https://github.com/ericcornelissen/shescape/issues/169.

Published by the source

3 Mar 2022, 19:26 UTC

Last modified by the source

8 Nov 2023, 04:08 UTC

Source last checked

26 Oct 2026, 12:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-446w-rrm4-r47f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-446w-rrm4-r47f

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

# Patch Next advisory brief: CVE-2022-24725

Advisory: Exposure of home directory through shescape on Unix with Bash
IDs: CVE-2022-24725, GHSA-446w-rrm4-r47f
Record: https://patchnext.com/advisories/cve-2022-24725 (revision 2, source checked 26 Oct 2026, 12:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: shescape 1.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm shescape: affected >= 1.4.0, < 1.5.1; fixed in 1.5.1

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

## 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 shescape.
- 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-446w-rrm4-r47f (OSV record GHSA-446w-rrm4-r47f lists affected ranges: npm shescape >=1.4.0 <1.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-446w-rrm4-r47f (GitHub-reviewed advisory GHSA-446w-rrm4-r47f lists affected ranges: npm shescape >=1.4.0 <1.5.1)

Commands are suggestions: review each one before running it.