{"items":[{"id":"NVI-00007991","kind":"vulnerability","title":"Composer: GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-96h3-5x6v-m776","CVE-2026-59944"],"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-5e928c4c994ee57a8a2d46fd5727eb3b"],"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.3 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"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.30 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"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-10-02T19:14:36.000Z","value":"6.1 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5e928c4c994ee57a8a2d46fd5727eb3b"}],"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-5e928c4c994ee57a8a2d46fd5727eb3b","url":"https://github.com/advisories/GHSA-96h3-5x6v-m776","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-96h3-5x6v-m776","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:40:00.567Z"},{"id":"sr-f185c5afb3c876b985113066d9ad6d37","url":"https://github.com/advisories/GHSA-96h3-5x6v-m776","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-96h3-5x6v-m776","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.680Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5e928c4c994ee57a8a2d46fd5727eb3b"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":[">= 2.3.0, < 2.10.3"]},{"certainty":"source_listed","source_ids":["sr-5e928c4c994ee57a8a2d46fd5727eb3b"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":[">= 1.0, < 2.2.30"]},{"certainty":"source_listed","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.10.3"]},{"certainty":"source_listed","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 2.2.30"]}],"null_published_at":"2026-11-01T07:29:12.920Z","source_updated_at":"2026-10-02T19:14:36.000Z","source_disclosed_at":"2026-10-02T19:14:34.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.680Z"},{"id":"NVI-00007991","kind":"vulnerability","title":"Composer: GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-96h3-5x6v-m776","CVE-2026-59944"],"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.3 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"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.30 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"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-f185c5afb3c876b985113066d9ad6d37","url":"https://github.com/advisories/GHSA-96h3-5x6v-m776","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-96h3-5x6v-m776","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.680Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.10.3"]},{"certainty":"source_listed","source_ids":["sr-f185c5afb3c876b985113066d9ad6d37"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"## 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 o","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 2.2.30"]}],"null_published_at":"2026-10-31T22:13:22.824Z","source_updated_at":"2026-10-02T19:30:06.432Z","source_disclosed_at":"2026-10-02T19:14:34.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:42:10.680Z"}],"next_cursor":null,"snapshot_revision":"42594"}