# The Jupyter notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.9, unauthorized actors can access sensitive information from server logs. Anytime a 5xx erro...

Advisory record · `GHSA-m87f-39q9-6f55`

- **Identifiers:** `GHSA-m87f-39q9-6f55` · `BIT-jupyter-base-notebook-2022-24758` · `BIT-jupyter-notebook-2022-24758` · `CVE-2022-24758` · `PYSEC-2022-180`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 31 Mar 2022
- **Updated:** 9 Oct 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 Mar 2022, 23:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `notebook` (PyPI): affected `<6.4.10`; fixed in `6.4.10`

## Machine-written summary

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

> Versions of the notebook package before 6.4.10 are vulnerable. When a 5xx error occurs, the server logs by default record the auth cookie and other header values, and those logs can be read without root access. An attacker who can read the logs can steal the auth cookie and gain access to the Jupyter server. Upgrade notebook to 6.4.10 or later; the source lists no workarounds.

Written 10 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.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

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

## Timeline

This record came from the full history of the GitHub Advisory Database, published 31 Mar 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-m87f-39q9-6f55](https://github.com/advisories/GHSA-m87f-39q9-6f55)
- [OSV: GHSA-m87f-39q9-6f55](https://osv.dev/vulnerability/GHSA-m87f-39q9-6f55)
- <https://github.com/jupyter/notebook/security/advisories/GHSA-m87f-39q9-6f55>

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-m87f-39q9-6f55>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m87f-39q9-6f55/>. Everything for agents: <https://agentprime.io/llms.txt>.
