{"items":[{"id":"NVI-00007939","kind":"vulnerability","title":"Composer: Arbitrary file write outside vendor via malicious transitive package name","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-499r-g7pc-vmp9","CVE-2026-59948"],"plain_summary":"GitHub lists this reviewed advisory for composer/composer, composer/composer. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-052e5b79c7a8b743977990d0f141f62b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.10.2 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.29 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-20T19:15:30.000Z","value":"7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-26e3013ae7003fbe621b58adfe27a136"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.138%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.03176. Missing scores are unknown.","source_id":"sr-052e5b79c7a8b743977990d0f141f62b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-26e3013ae7003fbe621b58adfe27a136","url":"https://github.com/advisories/GHSA-499r-g7pc-vmp9","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-499r-g7pc-vmp9","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"},{"id":"sr-eeb7fb806bf16c5f0bcbd946fa63bef9","url":"https://github.com/advisories/GHSA-499r-g7pc-vmp9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-499r-g7pc-vmp9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.667Z"},{"id":"sr-052e5b79c7a8b743977990d0f141f62b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-59948","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.789Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-26e3013ae7003fbe621b58adfe27a136"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":[">= 2.3.0, < 2.10.2"]},{"certainty":"source_listed","source_ids":["sr-26e3013ae7003fbe621b58adfe27a136"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":[">= 1.0.0, < 2.2.29"]},{"certainty":"source_listed","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.10.2"]},{"certainty":"source_listed","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":["ECOSYSTEM: introduced 1.0.0; fixed 2.2.29"]}],"null_published_at":"2026-11-04T10:04:41.546Z","source_updated_at":"2026-07-20T19:15:30.000Z","source_disclosed_at":"2026-07-20T19:15:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.667Z"},{"id":"NVI-00007939","kind":"vulnerability","title":"Composer: Arbitrary file write outside vendor via malicious transitive package name","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-499r-g7pc-vmp9","CVE-2026-59948"],"plain_summary":"OSV carries this publisher advisory for composer/composer, composer/composer. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.10.2 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.29 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-eeb7fb806bf16c5f0bcbd946fa63bef9","url":"https://github.com/advisories/GHSA-499r-g7pc-vmp9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-499r-g7pc-vmp9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.667Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.10.2"]},{"certainty":"source_listed","source_ids":["sr-eeb7fb806bf16c5f0bcbd946fa63bef9"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## Summary\n\nA maliciously crafted package, published on an untrusted third party repository other than Packagist.org or Private Packagist, can cause Composer to write files outside the `vendor/` directory and outside your project, with attacker-controlled content, during a normal `install` or `update` through using an invalid package name, which was not correctly validated by Composer.\n\nThis is an arbitrary file write that can be used to execute code outside the Composer project's context in which you expected the package code to execute (for example by writing shell startup files, SSH `authorized_keys`, or a cron entry). It is a supply-chain issue: it requires a malicious or compromised package to be present in the dependency graph, it is not otherwise remotely exploitable against a machine.\n\nThe fix makes Composer validate every package produced by dependency resolution before anything is written to `composer.lock` or installed, and abort with a security error if a package name is not a valid `vendor/package` name.\n\n## Am I affected?\n\nYou may be affected if you install packages from an untrusted third party repository, which does not sufficiently validate package names. Packagist","public_affected_ranges":["ECOSYSTEM: introduced 1.0.0; fixed 2.2.29"]}],"null_published_at":"2026-10-31T22:13:18.641Z","source_updated_at":"2026-07-20T19:30:24.128Z","source_disclosed_at":"2026-07-20T19:15:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.667Z"}],"next_cursor":null,"snapshot_revision":"42594"}