Skip to content
Noroxi
CVE-2026-40176· NVD / CVE Program· CNA GitHub_M

Composer is vulnerable to Command Injection via Malicious Perforce Repository

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.99% (FIRST EPSS); higher than 62% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: composer (Debian:12) 2.5.5-1+deb12u4; composer (Debian:13) 2.8.8-1+deb13u2; composer (Debian:14) 2.9.7-1.

Low priority for now. Upgrade to composer (Debian:12) 2.5.5-1+deb12u4; composer (Debian:13) 2.8.8-1+deb13u2; composer (Debian:14) 2.9.7-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Composer is a dependency manager for PHP. Versions 1.0 through 2.2.26 and 2.3 through 2.9.5 contain a command injection vulnerability in the Perforce::generateP4Command() method, which constructs shell commands by interpolating user-supplied Perforce connection parameters (port, user, client) without proper escaping. An attacker can inject arbitrary commands through these values in a malicious composer.json declaring a Perforce VCS repository, leading to command execution in the context of the user running Composer, even if Perforce is not installed. VCS repositories are only loaded from the root composer.json or the composer config directory, so this cannot be exploited through composer.json files of packages installed as dependencies. Users are at risk if they run Composer commands on untrusted projects with attacker-supplied composer.json files. This issue has been fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline).

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Apr 15, 2026
Updated
Jul 15, 2026
EPSS
0.9% · 62th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-40176

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for getcomposer records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
getcomposercomposer

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • getcomposer composer1.0.0 and later · up to 2.2.26 inclusive
  • getcomposer composer2.3.0 and later · up to 2.9.5 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • composer composer

    • >= 2.3, < 2.9.6, >= 1.0, < 2.2.27affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12composerbefore 2.5.5-1+deb12u42.5.5-1+deb12u4
Debian:13composerbefore 2.8.8-1+deb13u22.8.8-1+deb13u2
Debian:14composerbefore 2.9.7-12.9.7-1
openSUSE:Leap 16.0php-composer2before 2.8.9-160000.4.12.8.9-160000.4.1
openSUSE:Tumbleweedphp-composer2before 2.9.7-1.12.9.7-1.1
Packagistcomposer/composerfrom 1.0.0 · before 2.2.272.2.27
Packagistcomposer/composerfrom 2.3.0 · before 2.9.62.9.6
Red Hat:hummingbird:1composerbefore 0:2.9.7-1.hum10:2.9.7-1.hum1
SUSE:Linux Enterprise Module for Web and Scripting 15 SP7php-composer2before 2.6.4-150600.3.12.12.6.4-150600.3.12.1
SUSE:Linux Enterprise Server 16.0php-composer2before 2.8.9-160000.4.12.8.9-160000.4.1

Same product

getcomposer: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-41116Command injection in composer on Windows
    40Plan
  • CVE-2026-40261Composer has Command Injection via Malicious Perforce Reference
    36Monitor
  • CVE-2022-24828Missing input validation can lead to command execution in composer
    36Monitor
  • CVE-2021-29472Missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial in composer
    36Monitor
  • CVE-2023-43655Remote Code Execution via web-accessible composer.phar
    35Monitor
  • CVE-2015-8371Composer before 2016-02-10 allows cache poisoning from other projects built on the same host.
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:composer2.5.5-1+deb12u4 · Debian:12Package registry (OSV)
opensuse:php-composer22.9.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
Packagist:composer/composer2.2.27Package registry (OSV)
Packagist:composer/composer2.9.6Package registry (OSV)
red hat:composer0:2.9.7-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:php-composer22.8.9-160000.4.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:22026-04-16
Proof-of-concept repository on GitHubstars:02026-04-17
Proof-of-concept repository on GitHubstars:02026-06-15

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayOct 18, 2026+186 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-402610 days apartComposer has Command Injection via Malicious Perforce Reference
    36Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records