CVE-2025-67746 — Composer vulnerable to ANSI sequence injection
Composer is a dependency manager for PHP. In versions on the 2.x branch prior to 2.2.26 and 2.9.3, 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 we still publish a CVE as it has potential for abuse, and we want to be on the safe side informing users that they should upgrade. Versions 2.2.26 and 2.9.3 contain a patch for the issue.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Composer Composer, Getcomposer Composer).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Composer | Composer | version >= 2.0, < 2.2.26version >= 2.3, < 2.9.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Getcomposer | Composer | ≥ 2.0.0 and < 2.2.26≥ 2.3.0 and < 2.9.3 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 1.3 | CVSS 4.0 | Low | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 1.3 | CVSS 4.0 | Low | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
| 4.3 | CVSS 3.1 | Medium | 2.8 | 1.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.45%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · composer/composer
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 4.3
- Source status changed · → Analyzed
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- github.com/composer/composer/security/advisories/GHSA-59pp-r3rg-353g
- github.com/composer/composer/commit/1d40a95c9d39a6b7f80d404ab30336c586da9917
- github.com/composer/composer/commit/5db1876a76fdef76d3c4f8a27995c434c7a43e71
- github.com/composer/composer/releases/tag/2.2.26
- github.com/composer/composer/releases/tag/2.9.3
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-59944 Composer: CVE-2026-59946 fix bypass via symlinked package bin path 29d
- High CVE-2026-84361 Composer: Perforce source URL permits P4PORT `rsh:` command execution Sep 1, 2026
- High CVE-2026-45793 Composer: Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs Jul 15, 2026
- Medium CVE-2026-59946 Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files Jul 8, 2026
- Medium CVE-2026-59947 Composer: URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure) Jul 8, 2026
- High CVE-2026-59948 Composer: Arbitrary file write outside vendor via malicious transitive package name Jul 8, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-67746 is "Composer vulnerable to ANSI sequence injection", rated Medium. It affects Composer (Composer); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.45% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.