CVE-2026-59948

HIGHPre-NVD 7.07.0
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Composer is a dependency Manager for the PHP language. Prior to 2.2.29 and 2.10.2, a maliciously crafted package from an untrusted repository other than Packagist.org or Private Packagist can cause Composer to write attacker-controlled files outside the vendor directory and outside the project during install or update by using an invalid package name that is not correctly validated before dependency-resolution results are written or installed. This issue is fixed in versions 2.2.29 and 2.10.2.

CVSS v3
7.0
EG Score
7.0(low)
EPSS
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Arbitrary file write outside vendor via malicious transitive package name · Advisory · composer/composer · GitHub

https://github.com/composer/composer/security/advisories/GHSA-499r-g7pc-vmp9
github_release Patch Available

2.2.29

Patch available: composer/composer 2.2.29

https://github.com/composer/composer/releases/tag/2.2.29
github_release Patch Available

2.10.2

Patch available: composer/composer 2.10.2

https://github.com/composer/composer/releases/tag/2.10.2
github_commit Patch Available

commit c50b1efd13eb (composer/composer)

Patch available: composer/composer 2.2.29 (contains commit c50b1efd13eb)

https://github.com/composer/composer/commit/c50b1efd13ebd73f6dca19b31424c5a02bf93cc1
github_commit Patch Available

commit 502c6c4f6998 (composer/composer)

Patch available: composer/composer 2.10.2 (contains commit 502c6c4f6998)

https://github.com/composer/composer/commit/502c6c4f699802d9cf464728b3e8a95674f919a0

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-08 19:46 UTCEG score recompute
  2. 2026-07-08 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-59948?
CVE-2026-59948 is a high vulnerability published on July 8, 2026. Composer is a dependency Manager for the PHP language. Prior to 2.2.29 and 2.10.2, a maliciously crafted package from an untrusted repository other than Packagist.org or Private Packagist can cause Composer to write attacker-controlled files outside the vendor directory and outside the project…
When was CVE-2026-59948 disclosed?
CVE-2026-59948 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-59948?
CVE-2026-59948 has a CVSS v3 base score of 7.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59948?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59948, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59948

Explore →

Is Your Infrastructure Affected by CVE-2026-59948?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.