CVE-2025-67746

CVE-2025-67746 is a low-severity security vulnerability in composer/composer (composer), affecting versions >= 2.0.0, < 2.2.26. It is fixed in 2.2.26, 2.9.3.

Summary

Composer is vulnerable to ANSI sequence injection

Impact

Attackers controlling remote sources that Composer downloads from might in some way inject ANSI control characters in the terminal output of various Composer commands, causing mangled output and potentially leading to confusion or DoS of the terminal application.

There is no proven exploit and this has thus a low severity but Composer still published a CVE as it has potential for abuse, and Composer wants to be on the safe side informing users that they should upgrade.

Affected versions

composer/composer (>= 2.0.0, < 2.2.26) composer/composer (>= 2.3.0, < 2.9.3)

Security releases

composer/composer → 2.2.26 (composer) composer/composer → 2.9.3 (composer)

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.

See it in your environment

Remediation advice

2.2.26 for 2.2 LTS or 2.9.3 for mainline.

Frequently Asked Questions

  1. What is CVE-2025-67746? CVE-2025-67746 is a low-severity security vulnerability in composer/composer (composer), affecting versions >= 2.0.0, < 2.2.26. It is fixed in 2.2.26, 2.9.3.
  2. Which versions of composer/composer are affected by CVE-2025-67746? composer/composer (composer) versions >= 2.0.0, < 2.2.26 is affected.
  3. Is there a fix for CVE-2025-67746? Yes. CVE-2025-67746 is fixed in 2.2.26, 2.9.3. Upgrade to this version or later.
  4. Is CVE-2025-67746 exploitable, and should I be worried? Whether CVE-2025-67746 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
  5. What actually determines whether CVE-2025-67746 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.
  6. How do I fix CVE-2025-67746?
    • Upgrade composer/composer to 2.2.26 or later
    • Upgrade composer/composer to 2.9.3 or later

Other vulnerabilities in composer/composer

CVE-2026-40176CVE-2026-40261CVE-2025-67746CVE-2024-35241CVE-2024-35242

Stop the waste.
Protect your environment with Kodem.