critical

CVE-2022-41910

Heap overflow in `QuantizeAndDequantizeV2`

Published 6 Dec 2022Modified 17 Jun 2026CWE 125

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.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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

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

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

Description

TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.

Affected packages and fixed versions

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	2.8.4, 2.9.3, 2.10.1
pip::GitHub Security Advisory pip	tensorflow, tensorflow-cpu, tensorflow-gpu	2.8.4, 2.9.3, 2.10.1

Show all 4 entries from 2 sources

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	2.8.4, 2.9.3, 2.10.1
pip::GitHub Security Advisory pip	tensorflow	2.8.4, 2.9.3, 2.10.1
pip::GitHub Security Advisory pip	tensorflow-cpu	2.8.4, 2.9.3, 2.10.1
pip::GitHub Security Advisory pip	tensorflow-gpu	2.8.4, 2.9.3, 2.10.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