CVE-2026-25129

PsySH has Local Privilege Escalation via CWD .psysh.php auto-load

HIGH
7.3
CVSS Score
Published: January 30, 2026 at 08:12 PM UTC
Updated: June 17, 2026 at 10:24 AM UTC
2 products affected across 2 vendorsPsyshPsySH

Using psysh by bobthecow?

Get instant alerts when new vulnerabilities affect psysh - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.3
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

PsySH is a runtime developer console, interactive debugger, and REPL for PHP. Prior to versions 0.11.23 and 0.12.19, PsySH 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. This is a CWD configuration poisoning issue leading to arbitrary code execution in the victim user’s context. If a privileged user (e.g., root, a CI runner, or an ops/debug account) launches PsySH with CWD set to an attacker-writable directory containing a malicious `.psysh.php`, the attacker can execute commands with that privileged user’s permissions, resulting in local privilege escalation. Downstream consumers that embed PsySH inherit this risk. For example, Laravel Tinker (`php artisan tinker`) uses PsySH. If a privileged user runs Tinker while their shell is in an attacker-writable directory, the `.psysh.php` auto-load behavior can be abused in the same way to execute attacker-controlled code under the victim’s privileges. Versions 0.11.23 and 0.12.19 patch the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.11.230.12.0 ≤ v < 0.12.19
v < 0.11.23v < 0.12.19
Affected range stops below 0.11.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.12.19, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/bobthecow/psysh/security/advisories/GHSA-4486-gxhx-5mg7
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/bobthecow/psysh/releases/tag/v0.11.23
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/bobthecow/psysh/releases/tag/v0.12.19

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-427

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card