Command Injection in standard-version

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.

GitHub Security Lab (GHSL) Vulnerability Report: GHSL-2020-111 The GitHub Security Lab team has identified a potential security vulnerability in standard-version. Summary The standardVersion function has a command injection vulnerability. Clients of the standard-version library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. Product Standard Version Tested Version Commit 2f04ac8 Details Issue 1: Command injection in standardVersion The following proof-of-concept illustrates the vulnerability. First install Standard Version and create an empty git repo to run the PoC in: Now create a file with the following contents: and run it: Notice that a file named exploit has been created. This vulnerability is similar to command injection vulnerabilities that have been found in other Javascript libraries. Here are some examples: CVE-2020-7646, CVE-2020-7614, CVE-2020-7597, CVE-2019-10778, CVE-2019-10776, CVE-2018-16462, CVE-2018-16461,…

Published by the source

13 Jul 2020, 21:34 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-7xcx-6wjh-7xp2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7xcx-6wjh-7xp2

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

# Patch Next advisory brief: GHSA-7xcx-6wjh-7xp2

Advisory: Command Injection in standard-version
IDs: GHSA-7xcx-6wjh-7xp2
Record: https://patchnext.com/advisories/ghsa-7xcx-6wjh-7xp2 (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 fix available; fixed versions by package: standard-version 8.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm standard-version: affected < 8.0.1; fixed in 8.0.1

## Suggested inspection (read-only)
- `npm ls standard-version --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 standard-version.
- 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-7xcx-6wjh-7xp2 (OSV record GHSA-7xcx-6wjh-7xp2 lists affected ranges: npm standard-version >=0 <8.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-7xcx-6wjh-7xp2 (GitHub-reviewed advisory GHSA-7xcx-6wjh-7xp2 lists affected ranges: npm standard-version >=0 <8.0.1)

Commands are suggestions: review each one before running it.