CVE-2026-59946: Composer Path Traversal Vulnerability
MODERATECVE-2026-59946 is a MODERATE (CVSS 6.1) path traversal vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Composer libraries in the Packagist ecosystem. The issue involves path traversal in package bin field lets dependencies chmod arbitrary host files. Remediation is available by upgrading affected packages to version 2.10.2, 2.2.29.
CVE-2026-59946 at a Glance
Security Impact
CVSS: 6.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-59946
To remediate this vulnerability, upgrade all affected Composer dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade composer/composer to 2.10.2
Upgrade composer/composer to 2.2.29
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for composer/composer
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-59946, inspect your project dependencies for Composer:
inspect dependencies for composer/composer
Analyze the terminal output to locate any version of Composer in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.10.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-732: Incorrect Permission Assignment for Critical Resource, where the product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In Composer, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-59946 Affected Composer Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
composer/composer
|
Packagist |
≥ 2.3.0
< 2.10.2
|
2.10.2
|
|
composer/composer
|
Packagist |
≥ 1.0.0
< 2.2.29
|
2.2.29
|
References
Frequently Asked Questions
What is CVE-2026-59946?
Which Composer versions are affected?
What version fixes CVE-2026-59946?
Is composer/composer affected?
What is the CVSS score of CVE-2026-59946?
What CWE is associated with CVE-2026-59946?
How can I check Packagist dependencies for CVE-2026-59946?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gjfg-22fp-rrxx",
"modified" : "2026-07-20T21:57:40Z",
"published" : "2026-07-20T21:57:40Z",
"aliases" : [ "CVE-2026-59946" ],
"summary" : "Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files",
"details" : "## Summary\n\nA Composer package declares its executables in the `bin` field of its `composer.json`. When Composer installs a package, it processes each `bin` entry and changes the file mode of the corresponding file so it is executable.\n\nIf a `bin` entry contains `..` path segments, it can resolve to a path outside the package's own install directory. A malicious package can use this to make Composer run `chmod` against a file that already exists elsewhere on the machine. The resulting mode is world-readable and world-executable (0755 under the common umask of 022). This happens when the package is installed, e.g. during `composer install`, `composer update`, and `composer require`. Any dependency can trigger it, including a transitive dependency several levels deep.\n\nThe vulnerability *changes file permissions only, and does not read, modify, or execute the contents of the target file, and it is not remote code execution*. The impact is to confidentiality: a file with deliberately restrictive permissions, such as a private key at mode 0600, can be made readable by other users on the same host.\n\n## Am I affected?\n\nWe reviewed packagist.org data and found no evidence that any published package exploited this vulnerability. If you install packages only from packagist.org, you are not affected by any known exploitation.\n\nYou are potentially affected if *all* of the following are true:\n\n- Your Composer project depends, directly or transitively, on a package you do not fully trust.\n- A file you rely on for its restrictive permissions already exists at a path the Composer process can write to. Examples include SSH private keys, `.env` files, `~/.aws/credentials`, and `.netrc`.\n\nThe most likely way to be affected is to add or update a dependency that is malicious or has been compromised, then run an install on a machine that holds sensitive, permission-restricted files.\n\nTwo points to note:\n\n- `--no-scripts`, `--no-plugins`, and an `allow-plugins` allow-list do not prevent this. The permission change happens during normal binary installation, outside the plugin and script trust model.\n- Impact scales with privilege: As a regular user, only files owned by that user can be affected, which typically means your own secrets becoming readable by other local users on a shared machine. As root (for example, a CI container with no non-root user, or `sudo composer install`), any file on the system can be affected, including system credential stores.\n\n## Patched versions\n\nThe fix makes Composer reject any package whose binary entry contains a `..` path segment. During install/update the operation aborts before any file permission is changed, and the same check now also applies when a package is published to Packagist.org, so such packages are refused upstream.\n\nFixed in 2.2.29 (2.2 LTS line) and 2.10.2 (current 2.x line). Composer 1.x is end of life and will not be patched. 1.x users should upgrade to a patched 2.x release.\n\n## Workarounds\n\nUpgrading to a patched release is the only complete fix. There is no configuration option that disables the vulnerable behavior.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "composer/composer"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.3.0"
}, {
"fixed" : "2.10.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "composer/composer"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.0.0"
}, {
"fixed" : "2.2.29"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/composer/composer/security/advisories/GHSA-gjfg-22fp-rrxx"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59946"
}, {
"type" : "WEB",
"url" : "https://github.com/composer/composer/commit/502c6c4f699802d9cf464728b3e8a95674f919a0"
}, {
"type" : "WEB",
"url" : "https://github.com/composer/composer/commit/c50b1efd13ebd73f6dca19b31424c5a02bf93cc1"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/composer/composer"
}, {
"type" : "WEB",
"url" : "https://github.com/composer/composer/releases/tag/2.10.2"
}, {
"type" : "WEB",
"url" : "https://github.com/composer/composer/releases/tag/2.2.29"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22", "CWE-732" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-20T21:57:40Z",
"nvd_published_at" : "2026-07-08T20:16:59Z"
}
}