Summary
Workarounds
Make sure register_argc_argv is disabled in php.ini, and avoid publishing composer.phar to the web as this really should not happen.
Impact
Users publishing a composer.phar to a public web-accessible server where the composer.phar can be executed as a php file may be impacted if PHP also has register_argc_argv enabled in php.ini.
CVE-2023-43655 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.27, 2.2.22, 2.6.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
2.6.4, 2.2.22 and 1.10.27 patch this vulnerability.
Frequently Asked Questions
- What is CVE-2023-43655? CVE-2023-43655 is a high-severity security vulnerability in composer/composer (composer), affecting versions < 1.10.27. It is fixed in 1.10.27, 2.2.22, 2.6.4.
- How severe is CVE-2023-43655? CVE-2023-43655 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of composer/composer are affected by CVE-2023-43655? composer/composer (composer) versions < 1.10.27 is affected.
- Is there a fix for CVE-2023-43655? Yes. CVE-2023-43655 is fixed in 1.10.27, 2.2.22, 2.6.4. Upgrade to this version or later.
- Is CVE-2023-43655 exploitable, and should I be worried? Whether CVE-2023-43655 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-43655 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-43655?
- Upgrade
composer/composerto 1.10.27 or later - Upgrade
composer/composerto 2.2.22 or later - Upgrade
composer/composerto 2.6.4 or later
- Upgrade