cve.bz

CVE-2026-59944 composer composer: Path traversal

6.1 mediumEPSS 0.5%Fix available

Medium (6.1) in composer composer. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in composer/composer 2.10.3, 2.2.30.

On this page
Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and from 2.3.0 until 2.10.3, a malicious or compromised dependency can bypass the earlier CVE-2026-59946 binary-path hardening because Composer validates literal parent-directory segments only during dependency resolution, while the symlink and installed-metadata paths described by the advisory skip that validation. A package can ship an in-package binary symlink that resolves outside its installation directory, or attacker-influenced vendor/composer/installed.json metadata can provide an escaping binary path during a reinstall or regeneration of missing vendor/bin entries. The installed-metadata path is reachable only when the vendor directory was not populated by the same validated install run, such as when it is restored from an untrusted cache, copied from an earlier build stage, carried over from an older Composer run, or writable by a lower-trust build step. Composer can follow the path, change the external target's permissions to make it world-readable and executable, and create a runnable vendor/bin proxy to that external file. The issue does not directly read or transmit data and does not by itself provide remote code execution. This issue is fixed in versions 2.2.30 and 2.10.3.

Severity

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-59944 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59944?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59944?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59944 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
composer>= 1.0.0, < 2.2.30
composer>= 2.3.0, < 2.10.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-96h3-5x6v-m776Packagistcomposer/composer>=2.3.0 <2.10.32.10.3
GHSA-96h3-5x6v-m776Packagistcomposer/composer>=1.0 <2.2.302.2.30

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13composerno fix listedDEBIAN-CVE-2026-59944
Debian14composer2.10.3-1DEBIAN-CVE-2026-59944
Ubuntu26.04:LTS, 26.10, Pro:16.04:LTS and 4 morecomposerno fix listedUBUNTU-CVE-2026-59944
Red Hathummingbird:1composer0:2.10.3-1.hum1RHSA-2026:63151
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 5 morephp-composer22.2.30-150400.3.21.1SUSE-SU-2026:4283-1
SUSELinux Enterprise Module for Web and Scripting 15 SP7php-composer22.6.4-150600.3.23.1SUSE-SU-2026:4288-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0php-composer22.8.9-160000.6.1SUSE-SU-2026:23943-1
openSUSELeap 16.0php-composer22.8.9-160000.6.1openSUSE-SU-2026:21970-1
openSUSETumbleweedphp-composer22.10.3-1.1openSUSE-SU-2026:11633-1
Alpinev3.24composer2.10.3-r0ALPINE-CVE-2026-59944

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

Ensure the integrity of Composer's `vendor` directory and associated metadata. Avoid restoring `vendor` directories from untrusted caches or allowing lower-trust processes to modify them. Implement strict access controls on Composer project directories and perform Composer operations in a trusted, isolated build environment to prevent the introduction of malicious symlinks or metadata. This operational control may require adjustments to existing CI/CD pipelines or build processes.

ProductPackageStateAdvisory
Red Hat Hardened Imagescomposer-main-2.10.3-1.hum1Fixed 2026-09-03RHSA-2026:63151

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59944.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON