Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-1119

NIXPKGS-2026-1119
published on
Permalink CVE-2026-40176
7.8 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): REQUIRED
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 1 week, 6 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    13 packages
    • subtitlecomposer
    • composer-require-checker
    • haskellPackages.gogol-composer
    • phpPackages.cyclonedx-php-composer
    • php82Packages.cyclonedx-php-composer
    • php83Packages.cyclonedx-php-composer
    • php84Packages.cyclonedx-php-composer
    • php85Packages.cyclonedx-php-composer
    • phpPackages.composer-local-repo-plugin
    • php82Packages.composer-local-repo-plugin
    • php83Packages.composer-local-repo-plugin
    • php84Packages.composer-local-repo-plugin
    • php85Packages.composer-local-repo-plugin
  • @LeSuisse accepted
  • @LeSuisse ignored
    4 maintainers
    • @Ma27
    • @piotrkwiecinski
    • @aanderse
    • @talyz
    maintainer.ignore
  • @LeSuisse published on GitHub
Composer is vulnerable to Command Injection via Malicious Perforce Repository

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).

Affected products

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

Matching in nixpkgs

Ignored packages (13)

pkgs.composer-require-checker

CLI tool to check whether a specific composer package uses imported symbols that aren't part of its direct composer dependencies

Package maintainers

Ignored maintainers (4)