Cross-user code execution via shared configuration path
Published Jun 3, 2025 · Updated Jan 23, 2026
Uncontrolled search path handling in Project Jupyter Jupyter Core before 5.8.0 allows local users to execute code as another user. In jupyter_core/paths.py, SYSTEM_CONFIG_PATH and SYSTEM_JUPYTER_PATH include the shared PROGRAMDATA directory by default, allowing Jupyter applications to load attacker-written configuration. Exploitation requires a multi-user Windows host where an unprivileged user can write to that directory and a target user subsequently runs a Jupyter application.
Summary
What happened
Uncontrolled search path handling in Project Jupyter Jupyter Core before 5.8.0 allows local users to execute code as another user. In jupyter_core/paths.py, SYSTEM_CONFIG_PATH and SYSTEM_JUPYTER_PATH include the shared PROGRAMDATA directory by default, allowing Jupyter applications to load attacker-written configuration. Exploitation requires a multi-user Windows host where an unprivileged user can write to that directory and a target user subsequently runs a Jupyter application.
The record
- CVE
- CVE-2025-30167
- Published
- Jun 3, 2025
- Updated
- Jan 23, 2026
- Vendor
- Project Jupyter
- Product
- Jupyter Core
- Classifications
- CWE-427, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2025CVE publishedPublication date reported by the CVE source.
- Jan 23, 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=< 5.8.0
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.
Public exploit references
No public exploit references are available in this record.
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