critical

CVE-2022-23587

Integer overflow in TensorFlow

Published 4 Feb 2022Modified 17 Jun 2026CWE 190

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

GHSA8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Bitnami9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD, Bitnami. Rated lower by GHSA (high).

Description

Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

Affected packages and fixed versions

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	2.5.3, 2.6.3, 2.7.1
pip::GitHub Security Advisory pip	tensorflow, tensorflow-cpu, tensorflow-gpu	2.5.3, 2.6.3, 2.7.1

Show all 4 entries from 2 sources

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	2.5.3, 2.6.3, 2.7.1
pip::GitHub Security Advisory pip	tensorflow	2.5.3, 2.6.3, 2.7.1
pip::GitHub Security Advisory pip	tensorflow-cpu	2.5.3, 2.6.3, 2.7.1
pip::GitHub Security Advisory pip	tensorflow-gpu	2.5.3, 2.6.3, 2.7.1

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs