Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Improper escaping of command arguments on Windows leading to command injectionGHSA-frqg-7g38-6gcf

HIGHFix: composer/composer@ca5e2f8

GHSA-frqg-7g38-6gcf is a high-severity (CVSS 8.2) CWE-77 vulnerability in composer/composer. A fix is available for composer/composer — see the affected versions and patch details below.

Also known asBIT-composer-2021-41116CVE-2021-41116
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk-0.08%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.40%1.43%2.45%3.48%1.0%2.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-frqg-7g38-6gcf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐘composer/composer🐘composer/composer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Composer is an open source dependency manager for the PHP language. In affected versions windows users running Composer to install untrusted dependencies are subject to command injection and should upgrade their composer version. Other OSs and WSL are not affected. The issue has been resolved in composer versions 1.10.23 and 2.1.9. There are no workarounds for this issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcomposer/composerall versions1.10.23composer require composer/composer:^1.10.23
🐘Packagistcomposer/composer≥ 2.0.0-alpha1&&< 2.1.92.1.9composer require composer/composer:^2.1.9

Affected Products

2 products · 3 configurations
Application
composergetcomposer
≥ 2.0.0 && < 2.1.9
range
Application
tenable.sctenable
< 5.21.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for composer/composer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update composer/composer to 1.10.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-frqg-7g38-6gcf is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Windows users running Composer to install untrusted dependencies are affected and should definitely upgrade for safety. Other OSs and WSL are not affected. ### Patches 1.10.23 and 2.1.9 fix the issue ### Workarounds None
O3 Security · Impact-Aware SCA

Is GHSA-frqg-7g38-6gcf in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper escaping of command arguments on Windows…