Uncaught Exception Affecting jupyter-base-notebook package, versions <7.6.3-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.58% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-JUPYTERBASENOTEBOOK-20563100
  • published7 Oct 2026
  • disclosed13 Oct 2026

Introduced: 7 Oct 2026

NewCVE-2026-102599  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

Upgrade Wolfi jupyter-base-notebook to version 7.6.3-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jupyter-base-notebook package and not the jupyter-base-notebook package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

Socket.IO enables bidirectional and low-latency communication for every platform. From Engine.IO 6.6.0 until 6.6.10, a transport upgrade can independently derive an Engine.IO protocol revision from the upgrade request instead of enforcing the revision stored on the existing session. A malicious client can establish a valid session and send an upgrade request with a different or omitted EIO query parameter, attaching a transport with incompatible parser and heartbeat behavior. A crafted heartbeat packet can then trigger an uncaught exception and terminate the Node.js process, including when Engine.IO v3 compatibility is disabled because an omitted EIO value is interpreted as revision 3 on the affected path. This issue is fixed in Engine.IO 6.6.10.

CVSS Base Scores

version 3.1