Skip to content

Jupyter Core on Windows Has Uncontrolled Search Path Element Local Privilege Escalation Vulnerability

High severity GitHub Reviewed Published Jun 3, 2025 in jupyter/jupyter_core • Updated Jun 4, 2025

Package

pip jupyter_core (pip)

Affected versions

< 5.8.0

Patched versions

5.8.1

Description

Impact

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.

Mitigations

  • upgrade to jupyter_core>=5.8.1 (5.8.0 is patched but breaks jupyter-server) , or
  • 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)

Credit

Reported via Trend Micro Zero Day Initiative as ZDI-CAN-25932

References

@minrk minrk published to jupyter/jupyter_core Jun 3, 2025
Published by the National Vulnerability Database Jun 3, 2025
Published to the GitHub Advisory Database Jun 4, 2025
Reviewed Jun 4, 2025
Last updated Jun 4, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(1st percentile)

Weaknesses

CVE ID

CVE-2025-30167

GHSA ID

GHSA-33p9-3p43-82vq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.