{"items":[{"id":"NVI-00006839","kind":"vulnerability","title":"PsySH has Local Privilege Escalation via CWD .psysh.php auto-load","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-4486-gxhx-5mg7","CVE-2026-25129"],"plain_summary":"OSV carries this publisher advisory for psy/psysh, psy/psysh. 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 0.12.19 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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 0.11.23 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-221c7a67e876bd7556ee560997c0f0c2"],"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}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T10:24:09.540Z","value":"6.7 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-9b5bd30c52ffefbaeaea99a17e5d5934"},{"kind":"CVSS","as_of":"2026-06-17T10:24:09.540Z","value":"7.3 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-9b5bd30c52ffefbaeaea99a17e5d5934"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.322%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2524. Missing scores are unknown.","source_id":"sr-221c7a67e876bd7556ee560997c0f0c2"}],"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-c472a39f1a305faed92d3800b0509cc1","url":"https://github.com/advisories/GHSA-4486-gxhx-5mg7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4486-gxhx-5mg7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"},{"id":"sr-9b5bd30c52ffefbaeaea99a17e5d5934","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-25129","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-25129","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:47.597Z"},{"id":"sr-221c7a67e876bd7556ee560997c0f0c2","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-25129","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0.12.0; fixed 0.12.19"]},{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 0.11.23"]}],"null_published_at":"2026-11-06T15:18:11.509Z","source_updated_at":"2026-02-03T03:13:39.153Z","source_disclosed_at":"2026-01-30T21:28:44.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:41:49.663Z"},{"id":"NVI-00006839","kind":"vulnerability","title":"PsySH has Local Privilege Escalation via CWD .psysh.php auto-load","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4486-gxhx-5mg7","CVE-2026-25129"],"plain_summary":"OSV carries this publisher advisory for psy/psysh, psy/psysh. 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 0.12.19 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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 0.11.23 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-221c7a67e876bd7556ee560997c0f0c2"],"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}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.322%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2524. Missing scores are unknown.","source_id":"sr-221c7a67e876bd7556ee560997c0f0c2"}],"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-c472a39f1a305faed92d3800b0509cc1","url":"https://github.com/advisories/GHSA-4486-gxhx-5mg7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4486-gxhx-5mg7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"},{"id":"sr-221c7a67e876bd7556ee560997c0f0c2","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-25129","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0.12.0; fixed 0.12.19"]},{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 0.11.23"]}],"null_published_at":"2026-10-31T22:27:09.611Z","source_updated_at":"2026-02-03T03:13:39.153Z","source_disclosed_at":"2026-01-30T21:28:44.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.663Z"},{"id":"NVI-00006839","kind":"vulnerability","title":"PsySH has Local Privilege Escalation via CWD .psysh.php auto-load","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4486-gxhx-5mg7","CVE-2026-25129"],"plain_summary":"OSV carries this publisher advisory for psy/psysh, psy/psysh. 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 0.12.19 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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 0.11.23 for psy/psysh. Confirm the publisher’s latest guidance.","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"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-c472a39f1a305faed92d3800b0509cc1","url":"https://github.com/advisories/GHSA-4486-gxhx-5mg7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4486-gxhx-5mg7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0.12.0; fixed 0.12.19"]},{"certainty":"source_listed","source_ids":["sr-c472a39f1a305faed92d3800b0509cc1"],"technology":"psy/psysh","known_exclusions":[],"conditions_summary":"### Summary\nPsySH automatically loads and executes a `.psysh.php` file from the Current Working Directory (CWD) on startup. If an attacker can write to a directory that a victim later uses as their CWD when launching PsySH, the attacker can trigger arbitrary code execution in the victim's context. When the victim runs PsySH with elevated privileges (e.g., root), this results in local privilege escalation.\n\n### Details\nPsySH supports per-directory configuration via a `.psysh.php` file located in the process CWD. This file is executed implicitly when PsySH starts, without requiring explicit opt-in and without validating that the file and directory are safe (e.g., owned by the current user and not group/world-writable).\n\nThis enables a CWD poisoning scenario: a low-privileged user can plant a malicious `.psysh.php` in any directory they can write to, then wait for a higher-privileged user to start PsySH while their shell is in that directory.\n\n### PoC\n1. As a low-privileged user, create a malicious `.psysh.php` in an attacker-writable directory (example: `/tmp`):\n\n```bash\nbob@localhost:/tmp$ echo \" poc.txt'); ?>\" > .psysh.php\nbob@localhost:/tmp# ls -lah .psysh.php\n-r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 0.11.23"]}],"null_published_at":"2026-10-31T22:13:10.087Z","source_updated_at":"2026-02-03T03:13:39.153Z","source_disclosed_at":"2026-01-30T21:28:44.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.663Z"}],"next_cursor":null,"snapshot_revision":"42594"}