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

Advisory record · `GHSA-33p9-3p43-82vq`

- **Identifiers:** `GHSA-33p9-3p43-82vq` · `CVE-2025-30167` · `PYSEC-2026-1477`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-427](https://cwe.mitre.org/data/definitions/427.html)
- **Tags:** [CWE-427](https://agentprime.io/advisories/tag/cwe-427.md)
- **Published:** 4 Jun 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2025, 21:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `jupyter-core` (PyPI): affected `<5.8.1`; fixed in `5.8.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jupyter Core (jupyter-core) versions before 5.8.1 on Windows are vulnerable. The shared %PROGRAMDATA% directory is searched for configuration files, so a local user on a shared multi-user system with an unprotected %PROGRAMDATA% can create configuration files that affect other users, which the source describes as local privilege escalation. Upgrade to jupyter-core 5.8.1 or later; restricting write access to %PROGRAMDATA% or the %PROGRAMDATA%\jupyter directory also mitigates this.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.3 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 9th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-33p9-3p43-82vq)

## Sources

- [GitHub Advisory Database: GHSA-33p9-3p43-82vq](https://github.com/advisories/GHSA-33p9-3p43-82vq)
- [OSV: GHSA-33p9-3p43-82vq](https://osv.dev/vulnerability/GHSA-33p9-3p43-82vq)
- <https://github.com/jupyter/jupyter_core/security/advisories/GHSA-33p9-3p43-82vq>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-30167>
- <https://github.com/jupyter/jupyter_core/commit/5e8965600adda6b416692ce7e85ecb2bd814bd52>
- <https://github.com/jupyter/jupyter_core>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-33p9-3p43-82vq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-33p9-3p43-82vq/>. Everything for agents: <https://agentprime.io/llms.txt>.