Homepage

Information Exposure Through Log Files Affecting tensorflow-cpu-jupyter package, versions <2.21.0-r10

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (34th 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-CHAINGUARDLATEST-TENSORFLOWCPUJUPYTER-19958000
  • published20 Sept 2026
  • disclosed17 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 17 Sep 2026

NewCVE-2026-86049  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade Chainguard tensorflow-cpu-jupyter to version 2.21.0-r10 or higher.

NVD Description

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

Jupyter Server is the backend for Jupyter web applications. Prior to version 2.21.0, the 5xx request logging path in jupyter_server/log.py copies the Referer header into a JSON header block without applying the token scrubbing used for the request URI. A request that returns HTTP 500 while the Referer contains a token-bearing URL can therefore write that token to server logs in plaintext. An attacker who can read those logs can recover the token and use the affected user's Jupyter Server permissions. This issue is fixed in version 2.21.0.