Command injection in gh-ost

Exploitation

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

CVSS

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

EPSS

• CVE-2022-21687: 1.00% estimated exploitation activity in the next 30 days; percentile 62.98 (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.

Gh-ost version <= 1.1.2 allows users to inject DSN strings via the -database parameter. This is a low severity vulnerability as the attacker must have access to the target host or trick an administrator into executing a malicious gh-ost command on a host running gh-ost, plus network access from host running gh-ost to the attack's malicious MySQL server. Impact This issue may lead to arbitrary local file read. Patches Fixed in 1.1.3+. Workarounds None References - https://advisory.dw1.io/51 For more information If you have any questions or comments about this advisory: Open an issue in github/gh-ost

Published by the source

1 Feb 2022, 00:47 UTC

Last modified by the source

3 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rrp4-2xx3-mv29

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

# Patch Next advisory brief: CVE-2022-21687

Advisory: Command injection in gh-ost
IDs: CVE-2022-21687, GHSA-rrp4-2xx3-mv29
Record: https://patchnext.com/advisories/cve-2022-21687 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/github/gh-ost 1.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/github/gh-ost: affected < 1.1.3; fixed in 1.1.3

## Suggested inspection (read-only)
- Go github.com/github/gh-ost: check the installed version with your package manager.

## 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 github.com/github/gh-ost.
- 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://github.com/advisories/GHSA-rrp4-2xx3-mv29 (GitHub-reviewed advisory GHSA-rrp4-2xx3-mv29 lists affected ranges: Go github.com/github/gh-ost >=0 <1.1.3)

Commands are suggestions: review each one before running it.