Homepage

CVE-2026-4800 The advisory has been revoked - it doesn't affect any version of package tensorflow-cpu-jupyter  (opens in a new tab)

Threat Intelligence

Social Trends
Trending on 𝕏
EPSS
2.81% (87th 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-17984914
  • published16 Jul 2026
  • disclosed31 Mar 2026
Report a new vulnerability Found a mistake?

Introduced: 31 Mar 2026

CVE-2026-4800  (opens in a new tab)

Amendment

The Wolfi security team deemed this advisory irrelevant for Wolfi:latest.

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.

The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only developer-controlled, static key names.

References