SafeInstall agent guard shell parsing can miss raw package execution

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary SafeInstall CLI through 0.10.1 can fail to recognize some package-manager and registry-runner commands in its agent guard. Case-variant launcher names, leading file-descriptor redirections, and supported shell wrappers with options can cause a raw install command to receive no guard decision. Remote project scaffolding through package-manager create/init commands can also avoid the approval decision used for other registry runners. Impact When the SafeInstall guard is installed for a coding agent, a crafted shell command can bypass the intended deny or ask response. The coding agent may then run a package installation or registry-provided scaffolding command without SafeInstall policy evaluation and without SafeInstall enforcing disabled lifecycle scripts. Exploitation requires a coding agent to act on attacker-influenced instructions and issue the crafted shell command. A successful malicious package or runner can execute with the permissions of the developer account,…

Published by the source

10 Jul 2026, 19:34 UTC

Last modified by the source

10 Jul 2026, 19:45 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xrmc-c5cg-rv7x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xrmc-c5cg-rv7x

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

# Patch Next advisory brief: GHSA-xrmc-c5cg-rv7x

Advisory: SafeInstall agent guard shell parsing can miss raw package execution
IDs: GHSA-xrmc-c5cg-rv7x
Record: https://patchnext.com/advisories/ghsa-xrmc-c5cg-rv7x (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: safeinstall-cli 0.10.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm safeinstall-cli: affected < 0.10.2; fixed in 0.10.2

## Suggested inspection (read-only)
- `npm ls safeinstall-cli --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 safeinstall-cli.
- 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-xrmc-c5cg-rv7x (OSV record GHSA-xrmc-c5cg-rv7x lists affected ranges: npm safeinstall-cli >=0 <0.10.2 (fixed))
- Verified: https://github.com/advisories/GHSA-xrmc-c5cg-rv7x (GitHub-reviewed advisory GHSA-xrmc-c5cg-rv7x lists affected ranges: npm safeinstall-cli >=0 <0.10.2)

Commands are suggestions: review each one before running it.