How severe is GHSA-x7cr-6qr6-2hh6?

GHSA-x7cr-6qr6-2hh6 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x7cr-6qr6-2hh6?

GHSA-x7cr-6qr6-2hh6 affects the following packages: composer/composer (Packagist), composer/composer (Packagist), composer/composer (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-x7cr-6qr6-2hh6?

Update composer/composer to 1.10.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7cr-6qr6-2hh6 is resolved across your whole dependency graph.

How do I detect GHSA-x7cr-6qr6-2hh6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for composer/composer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-x7cr-6qr6-2hh6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x7cr-6qr6-2hh6?

O3 pinpoints whether GHSA-x7cr-6qr6-2hh6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x7cr-6qr6-2hh6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x7cr-6qr6-2hh6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x7cr-6qr6-2hh6?

GHSA-x7cr-6qr6-2hh6 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x7cr-6qr6-2hh6?

GHSA-x7cr-6qr6-2hh6 is classified as Improper Input Validation (CWE-20), CWE-88 (CWE-88). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x7cr-6qr6-2hh6 published, and has it been updated?

GHSA-x7cr-6qr6-2hh6 was published on April 22, 2022 and was last updated on February 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-x7cr-6qr6-2hh6

HIGH

Missing input validation can lead to command execution in composer

Also known asBIT-composer-2022-24828CVE-2022-24828

Published

Apr 22, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk75th percentile+1.57%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐘composer/composer🐘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

The Composer method VcsDriver::getFileContent() with user-controlled $file or $identifier arguments is susceptible to an argument injection vulnerability. It can be leveraged to gain arbitrary command execution if the Mercurial or the Git driver are used.

This led to a vulnerability on Packagist.org and Private Packagist, i.e., using the composer.json readme field as a vector for injecting parameters into the $file argument for the Mercurial driver or via the $identifier argument for the Git and Mercurial drivers.

Composer itself can be attacked through branch names by anyone controlling a Git or Mercurial repository, which is explicitly listed by URL in a project's composer.json.

To the best of our knowledge, this was not actively exploited. The vulnerability has been patched on Packagist.org and Private Packagist within a day of the vulnerability report.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`composer/composer`	all versions	1.10.26
🐘Packagist	`composer/composer`	≥ 2.0&&< 2.2.12	2.2.12
🐘Packagist	`composer/composer`	≥ 2.3&&< 2.3.5	2.3.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for composer/composer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update composer/composer to 1.10.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7cr-6qr6-2hh6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x7cr-6qr6-2hh6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x7cr-6qr6-2hh6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Composer method `VcsDriver::getFileContent()` with user-controlled `$file` or `$identifier` arguments is susceptible to an argument injection vulnerability. It can be leveraged to gain arbitrary command execution if the Mercurial or the Git driver are used. This led to a vulnerability on Packagist.org and Private Packagist, i.e., using the composer.json `readme` field as a vector for injecting parameters into the `$file` argument for the Mercurial driver or via the `$identifier` argument for the Git and Mercurial drivers. Composer itself can be attacked through branch names by anyone con

O3 Security · Impact-Aware SCA

Is GHSA-x7cr-6qr6-2hh6 in your dependencies?

O3 detects GHSA-x7cr-6qr6-2hh6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works