cve.bz

CVE-2022-41911 google tensorflow: Incorrect Type Conversion or Cast

7.5 highEPSS 0.6%Fix available

High (7.5) in google tensorflow. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.10.1, 2.8.4, 2.9.3.

On this page
TensorFlow is an open source platform for machine learning. When printing a tensor, we get it's data as a `const char*` array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from `char` to `bool` are undefined if the `char` is not `0` or `1`, so sanitizers/fuzzers will crash. The issue has been patched in GitHub commit `1be74370327`. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.10.1, TensorFlow 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-704 Incorrect Type Conversion or Cast
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-41911 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-41911?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-41911?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-41911 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
google:tensorflowbefore 2.8.4
google:tensorflowfrom 2.9.0 before 2.9.3
google:tensorflow2.10.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pf36-r9c6-h97jPyPItensorflow<2.8.42.8.4
GHSA-pf36-r9c6-h97jPyPItensorflow-cpu>=2.9.0 <2.9.32.9.3
GHSA-pf36-r9c6-h97jPyPItensorflow-gpu>=2.10.0 <2.10.12.10.1
GHSA-pf36-r9c6-h97jPyPItensorflow>=2.9.0 <2.9.32.9.3
GHSA-pf36-r9c6-h97jPyPItensorflow>=2.10.0 <2.10.12.10.1
GHSA-pf36-r9c6-h97jPyPItensorflow-cpu<2.8.42.8.4
GHSA-pf36-r9c6-h97jPyPItensorflow-gpu<2.8.42.8.4
GHSA-pf36-r9c6-h97jPyPItensorflow-gpu>=2.9.0 <2.9.32.9.3
GHSA-pf36-r9c6-h97jPyPItensorflow-cpu>=2.10.0 <2.10.12.10.1
PYSEC-2026-1954PyPItensorflow-gpu<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1
PYSEC-2026-3222PyPItensorflow<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1
PYSEC-2026-939PyPItensorflow-cpu<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux2tensorflow2.11.0-1AZL-11544

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

References

Check your stackJSON