Local privilege escalation via CWD config auto-load
Published Jan 30, 2026 · Updated Jan 30, 2026
Local privilege escalation in PsySH before 0.11.23 and 0.12.0 through 0.12.18 allows local users to execute code as a victim. At startup, the project-config loader implicitly executes .psysh.php from the current working directory without checking ownership or writability. Exploitation requires an attacker-writable directory to become the working directory when a more-privileged user launches PsySH, granting that user's permissions.
Summary
What happened
Local privilege escalation in PsySH before 0.11.23 and 0.12.0 through 0.12.18 allows local users to execute code as a victim. At startup, the project-config loader implicitly executes .psysh.php from the current working directory without checking ownership or writability. Exploitation requires an attacker-writable directory to become the working directory when a more-privileged user launches PsySH, granting that user's permissions.
The record
- CVE
- CVE-2026-25129
- Published
- Jan 30, 2026
- Updated
- Jan 30, 2026
- Vendor
- bobthecow
- Product
- PsySH
- Classifications
- CWE-427, CAPEC-38, CAPEC-471, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2026CVE publishedPublication date reported by the CVE source.
- Jan 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.11.23
- Affected versionversion=>= 0.12.0, < 0.12.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream CWD configuration-poisoning proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo