CVE-2026-59944: Composer GHSA-gjfg-22fp-rrxx Fix Bypass Vulnerability

MODERATE
Advisory Identifier: GHSA-96h3-5x6v-m776
CVSS 6.1
CWE-732 CWE-59 CWE-22
Published
Advisory Summary

CVE-2026-59944 is a MODERATE (CVSS 6.1) ghsa-gjfg-22fp-rrxx fix bypass vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Composer libraries in the Packagist ecosystem. The issue involves ghsa-gjfg-22fp-rrxx fix bypass via symlinked package bin path. Remediation is available by upgrading affected packages to version 2.10.3, 2.2.30.

CVE-2026-59944 at a Glance

CVE Identifier CVE-2026-59944
GHSA Identifier GHSA-96h3-5x6v-m776
Severity MODERATE
CVSS v3.1 Base Score 6.1
CWE Classification CWE-732: Incorrect Permission Assignment for Critical Resource
Affected Product Composer
Package Ecosystem Packagist
Published Date
Last Updated

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-59944

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.

composer/composer fixed: 2.10.3
Upgrade composer/composer to 2.10.3
composer/composer fixed: 2.2.30
Upgrade composer/composer to 2.2.30
Verify Direct and Transitive Dependencies

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-59944, 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.3), 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

## Summary A malicious or compromised Composer package could, when installed as a dependency, cause Composer to change the permissions of a file outside that package's own directory and to register a runnable `vendor/bin` command that points at that outside file. This is a path traversal and link following issue. It is not remote code execution, the attacker gains no ability to read or receive your data directly. The risk is that a file which was readable only by its owner, but modifiable by Composer, can be made world readable and executable, which is enough to expose its contents on a shared or multi tenant host. The earlier hardening from GHSA-gjfg-22fp-rrxx can be bypassed, since it only rejected literal `..` path segments in a package's declared binaries, and was only applied in a single place during dependency resolution. ## Am I affected? You can be affected if a malicious or compromised package, including a transitive dependency, is installed in your project, and either of the following is true: - The dependency package ships one of its declared binaries as a symbolic link that resolves to a location outside the package's own directory. Nothing beyond a normal install or update is required. - Or, the recorded metadata of your installed dependencies (`vendor/composer/installed.json`) declares a binary path that escapes the package's directory. Composer regenerates missing binaries from that recorded metadata at the end of an install, and uses this metadata for reinstalls of the same package. In both of these cases the validation applied during dependency resolution is skipped. This situation is only reachable when your `vendor` directory is not populated from the same install run, which performs validation. For example a vendor directory restored from a shared or untrusted CI cache, copied in from an earlier container build stage, carried over from a Composer older than 2.10.2 or 2.2.29, or writable by a lower trust build step, could contain such malicious data. The most realistic way to get hit is a `composer install` in a build or deploy step that reuses a `vendor` directory produced elsewhere, since the permission change is applied silently and with the privileges of the user running Composer. ## Patched versions Composer now verifies that each declared binary resolves to a path inside the installing package's own directory before it touches the file, and skips any binary that resolves outside it with a warning. Update to the patched releases (2.10.3 and 2.2.30). ## Workarounds Upgrading is the only complete fix.

CVE-2026-59944 Affected Composer Versions

2 component(s)
Fixed Versions:
2.10.32.2.30
Product / Package Ecosystem Affected Versions Fixed Version
composer/composer
Packagist
≥ 2.3.0
< 2.10.3
2.10.3
composer/composer
Packagist
≥ 1.0
< 2.2.30
2.2.30

References

Frequently Asked Questions

What is CVE-2026-59944?
CVE-2026-59944 is a security vulnerability in Composer involving GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path under CWE-732: Incorrect Permission Assignment for Critical Resource.
Which Composer versions are affected?
Affected versions include releases prior to 2.10.3, 2.2.30 across affected packages: composer/composer.
What version fixes CVE-2026-59944?
Upgrading to 2.10.3, 2.2.30 (or the latest patched release for your respective branch) resolves the vulnerability.
Is composer/composer affected?
Yes, composer/composer is affected in releases prior to 2.10.3, 2.2.30. Upgrade your dependency to 2.10.3, 2.2.30 or later.
What is the CVSS score of CVE-2026-59944?
CVE-2026-59944 has a CVSS v3.1 base score of 6.1 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2026-59944?
CVE-2026-59944 is classified under CWE-732: Incorrect Permission Assignment for Critical Resource (The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.).
How can I check Packagist dependencies for CVE-2026-59944?
Run the dependency tree command: 'inspect dependencies for composer/composer'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-96h3-5x6v-m776",
  "modified" : "2026-10-02T19:14:34Z",
  "published" : "2026-10-02T19:14:34Z",
  "aliases" : [ "CVE-2026-59944" ],
  "summary" : "Composer: GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path",
  "details" : "## Summary\n\nA malicious or compromised Composer package could, when installed as a dependency, cause Composer to change the permissions of a file outside that package's own directory and to register a runnable `vendor/bin` command that points at that outside file. This is a path traversal and link following issue. It is not remote code execution, the attacker gains no ability to read or receive your data directly. The risk is that a file which was readable only by its owner, but modifiable by Composer, can be made world readable and executable, which is enough to expose its contents on a shared or multi tenant host. The earlier hardening from GHSA-gjfg-22fp-rrxx can be bypassed, since it only rejected literal `..` path segments in a package's declared binaries, and was only applied in a single place during dependency resolution.\n\n## Am I affected?\n\nYou can be affected if a malicious or compromised package, including a transitive dependency, is installed in your project, and either of the following is true:\n\n- The dependency package ships one of its declared binaries as a symbolic link that resolves to a location outside the package's own directory. Nothing beyond a normal install or update is required.\n- Or, the recorded metadata of your installed dependencies (`vendor/composer/installed.json`) declares a binary path that escapes the package's directory. Composer regenerates missing binaries from that recorded metadata at the end of an install, and uses this metadata for reinstalls of the same package. In both of these cases the validation applied during dependency resolution is skipped. This situation is only reachable when your `vendor` directory is not populated from the same install run, which performs validation. For example a vendor directory restored from a shared or untrusted CI cache, copied in from an earlier container build stage, carried over from a Composer older than 2.10.2 or 2.2.29, or writable by a lower trust build step, could contain such malicious data.\n\nThe most realistic way to get hit is a `composer install` in a build or deploy step that reuses a `vendor` directory produced elsewhere, since the permission change is applied silently and with the privileges of the user running Composer.\n\n## Patched versions\n\nComposer now verifies that each declared binary resolves to a path inside the installing package's own directory before it touches the file, and skips any binary that resolves outside it with a warning. Update to the patched releases (2.10.3 and 2.2.30).\n\n## Workarounds\n\nUpgrading is the only complete fix.",
  "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.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "composer/composer"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0"
      }, {
        "fixed" : "2.2.30"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/composer/composer/security/advisories/GHSA-96h3-5x6v-m776"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59944"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/composer/composer/commit/53b8bb4c24697b2f00a18cf1ef35a10392701b89"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/composer/composer/commit/ad649fdfdf8ed826d4a34e0e5690c76a0b4833aa"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/composer/composer"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/composer/composer/releases/tag/2.10.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/composer/composer/releases/tag/2.2.30"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-59", "CWE-732" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-02T19:14:34Z",
    "nvd_published_at" : "2026-09-16T17:17:28Z"
  }
}