CVE-2026-59948

Arbitrary file write via unvalidated package names

Published Jul 8, 2026 · Updated Jul 8, 2026

Path traversal in Composer 1.0 through 2.2.28 and 2.3.0 through 2.10.1 allows attackers to write files outside a project. LockTransaction::setResultPackages accepts dependency-solver packages loaded through nonvalidating ArrayLoader paths and writes or installs them without rechecking vendor/package names. Exploitation requires an install or update that resolves a malicious or compromised package from an untrusted third-party repository; crafted names can place startup, SSH authorization, or cron files under the Composer process account.

CVSS severity7.0
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in Composer 1.0 through 2.2.28 and 2.3.0 through 2.10.1 allows attackers to write files outside a project. LockTransaction::setResultPackages accepts dependency-solver packages loaded through nonvalidating ArrayLoader paths and writes or installs them without rechecking vendor/package names. Exploitation requires an install or update that resolves a malicious or compromised package from an untrusted third-party repository; crafted names can place startup, SSH authorization, or cron files under the Composer process account.

The record

CVE
CVE-2026-59948
Published
Jul 8, 2026
Updated
Jul 8, 2026
Vendor
Composer
Product
Composer
Classifications
CWE-22, CWE-787, T1195.001
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.0, < 2.2.29
  2. Affected versionversion=>= 2.3.0, < 2.10.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Composer · Composerversion=>= 1.0, < 2.2.29; version=>= 2.3.0, < 2.10.2

Published CVSS scores

7.0GitHub, Inc.CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CWE-787Out-of-bounds Write
T1195.001Compromise Software Dependencies and Development Tools

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo