CVE-2022-24758: Jupyter Notebook Unauthorized Access to Server Logs

notebook Updated 02 Oct 2025

Summary

31/03/2022
Yes i
High
7.5

CVE-2022-24758: The Jupyter notebook is a web-based notebook environment for interactive computing. Affects notebook versions < 6.4.10. Fixed in 6.4.10. How to fix ↓

Also tracked for

The same CVE-2022-24758 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Jupyter notebook is a web-based notebook environment for interactive computing. It allows users to create and share documents that contain live code, equations, visualizations, and narrative text. The notebook interface is widely used in data science and scientific computing communities. Jupyter notebook version 6.4.9 and earlier are vulnerable to unauthorized access to sensitive information from server logs.

Vulnerability Detail

The vulnerability in Jupyter notebook allows unauthorized actors to access sensitive information from server logs. Whenever a 5xx error is triggered, the authentication cookie and other header values are recorded in the Jupyter server logs by default. Since these logs can be accessed without root privileges, an attacker can monitor the logs, steal the sensitive authentication and cookie information, and gain unauthorized access to the Jupyter server. The vulnerability has been assigned CVE-2022-24758 and GHSA-m87f-39q9-6f55.

How To Fix

Latest published version: 7.6.3 as of 22 Oct 2026

pip install --upgrade "notebook==7.6.3"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

6.4.10

This is the first release that contains the fix.

pip install --upgrade "notebook==6.4.10"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The vulnerability in Jupyter notebook allows unauthorized access to sensitive information from server logs. Upgrading to Jupyter notebook version 6.4.10 or later is the recommended solution to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for notebook →

Share this vulnerability

FAQ

Jupyter notebook is a web-based notebook environment for interactive computing. It allows users to create and share documents that contain live code, equations, visualizations, and narrative text.

The vulnerability allows unauthorized actors to access sensitive information from server logs. This can lead to unauthorized access to the Jupyter server and potential misuse of the stolen authentication and cookie information.

Jupyter notebook versions 6.4.9 and earlier are affected by this vulnerability.

To fix this vulnerability, upgrade Jupyter notebook to version 6.4.10 or later.

There are currently no known workarounds for this vulnerability. Upgrading to the latest version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for notebook.

How To Fix

Latest published version: 7.6.3 as of 22 Oct 2026

pip install --upgrade "notebook==7.6.3"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

6.4.10

This is the first release that contains the fix.

pip install --upgrade "notebook==6.4.10"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback