CVE-2025-30167 | Jupyter Core on Windows Has Uncontrolled Search Path Element Local Privilege Escalation Vulnerability

Jupyter Core is a package for the core common functionality of Jupyter projects. When using Jupyter Core prior to version 5.8.0 on Windows, the shared `%PROGRAMDATA%` directory is searched for configuration files (`SYSTEM_CONFIG_PATH` and `SYSTEM_JUPYTER_PATH`), which may allow users to create configuration files affecting other users. Only shared Windows systems with multiple users and unprotected `%PROGRAMDATA%` are affected. Users should upgrade to Jupyter Core version 5.8.0 or later to receive a patch. Some other mitigations are available. As administrator, modify the permissions on the `%PROGRAMDATA%` directory so it is not writable by unauthorized users; or as administrator, create the `%PROGRAMDATA%\jupyter` directory with appropriately restrictive permissions; or as user or administrator, set the `%PROGRAMDATA%` environment variable to a directory with appropriately restrictive permissions (e.g. controlled by administrators _or_ the current user).

Published: 2025-06-03 Last update: 2026-01-23 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-30167 is rated Low Risk (36/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-30167

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-30 0.01% 0.06% +0.05%
2 2025-06-04 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-30167

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.3 5.9 [email protected]

Weakness enumeration for CVE-2025-30167

GitHub Security Advisory for CVE-2025-30167

GHSA-33p9-3p43-82vq · Severity: high · Ecosystem: pip — Jupyter Core on Windows Has Uncontrolled Search Path Element Local Privilege Escalation Vulnerability

OS Trackers for CVE-2025-30167

vendor priority summary link
debian unimportant CVE-2025-30167 unimportant priority: Debian including 1 source packages (jupyter-core), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-30167
ubuntu medium CVE-2025-30167 medium priority: Ubuntu including 1 source packages (jupyter-core), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 6, ignored 2. https://ubuntu.com/security/CVE-2025-30167

Affected software / configurations for CVE-2025-30167

Vendor Product Version Raw CPE
jupyter jupyter_core < 5.8.0 cpe:2.3:a:jupyter:jupyter_core:*:*:*:*:*:*:*:*

References for CVE-2025-30167

cvelogic Threat Intelligence