Improper Handling of Windows Device Names Affecting tensorflow-cpu-jupyter package, versions <2.20.0-r8


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.44% (37th 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-TENSORFLOWCPUJUPYTER-15417091
  • published5 Mar 2026
  • disclosed8 Jan 2026

Introduced: 8 Jan 2026

CVE-2026-21860  (opens in a new tab)
CWE-67  (opens in a new tab)

How to fix?

Upgrade Wolfi tensorflow-cpu-jupyter to version 2.20.0-r8 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 Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

Werkzeug is a comprehensive WSGI web application library. Prior to version 3.1.5, Werkzeug's safe_join function allows path segments with Windows device names that have file extensions or trailing spaces. On Windows, there are special device names such as CON, AUX, etc that are implicitly present and readable in every directory. Windows still accepts them with any file extension, such as CON.txt, or trailing spaces such as CON. This issue has been patched in version 3.1.5.

CVSS Base Scores

version 3.1