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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-30167: 0.20% estimated exploitation activity in the next 30 days; percentile 9.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

4 Jun 2025, 21:00 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

24 Oct 2026, 04:13 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-33p9-3p43-82vq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30167

Advisory: Jupyter Core on Windows Has Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
IDs: CVE-2025-30167, GHSA-33p9-3p43-82vq
Record: https://patchnext.com/advisories/cve-2025-30167 (revision 1, source checked 24 Oct 2026, 04:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jupyter-core 5.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI jupyter-core: affected < 5.8.1; fixed in 5.8.1

## Suggested inspection (read-only)
- `python -m pip show jupyter-core`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jupyter-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-33p9-3p43-82vq (OSV record GHSA-33p9-3p43-82vq lists affected ranges: PyPI jupyter-core >=0 <5.8.1 (fixed))

Commands are suggestions: review each one before running it.