CVE-2025-30167 json
Jupyter Core on Windows Has Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
published last yr. modified last mo. also EUVD-2025-16771 , GHSA-33p9-3p43-82vq , PYSEC-2026-1477
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- pypi jupyter-core 5.8.1
- jupyter jupyter_core 5.8.0
- python-jupyter-core openSUSE Tumbleweed 5.8.1-1.1
opensuse advisories openSUSE-SU-2025:15272-1
Is CVE-2025-30167 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | jupyter-core | <5.8.1 |
5.8.1 |
Affected products
- jupyter jupyter_core
Classification
- Weakness
-
- CWE-427 Uncontrolled Search Path Element
References
-
github.com
/jupyter/jupyter_core/commit/5e8965600adda6b416692ce7e85ecb2bd814bd52
web
-
github.com
/jupyter/jupyter_core/security/advisories/GHSA-33p9-3p43-82vq
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-30167
advisory
-
github.com
/jupyter/jupyter_core
package
-
pypi.org
/project/jupyter-core
package
-
github.com
/advisories/GHSA-33p9-3p43-82vq
advisory
Sources
- CVE List CVE-2025-30167
- GitHub Advisory GHSA-33p9-3p43-82vq
- NVD CVE-2025-30167
- OSV PYSEC-2026-1477
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.