cve.bz

CVE-2022-29209 google tensorflow: Type Confusion

5.5 mediumExploit referenceEPSS 0.4%Fix available

Medium (5.5) in google tensorflow. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.6.4, 2.7.2, 2.8.1.

On this page
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the macros that TensorFlow uses for writing assertions (e.g., `CHECK_LT`, `CHECK_GT`, etc.) have an incorrect logic when comparing `size_t` and `int` values. Due to type conversion rules, several of the macros would trigger incorrectly. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-04-22. 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-843 Access of Resource Using Incompatible Type (Type Confusion)
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-29209 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-29209?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-29209?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-29209 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.6.4
google:tensorflowfrom 2.7.0 before 2.7.2
google:tensorflow2.7.0:rc0
google:tensorflow2.7.0:rc1
google:tensorflow2.8.0
google:tensorflow2.8.0:rc0
google:tensorflow2.8.0:rc1
google:tensorflow2.9.0:rc0
google:tensorflow2.9.0:rc1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f4rr-5m7v-wxcwPyPItensorflow<2.6.42.6.4
GHSA-f4rr-5m7v-wxcwPyPItensorflow>=2.7.0 <2.7.22.7.2
GHSA-f4rr-5m7v-wxcwPyPItensorflow>=2.8.0 <2.8.12.8.1
GHSA-f4rr-5m7v-wxcwPyPItensorflow-cpu<2.6.42.6.4
GHSA-f4rr-5m7v-wxcwPyPItensorflow-cpu>=2.7.0 <2.7.22.7.2
GHSA-f4rr-5m7v-wxcwPyPItensorflow-cpu>=2.8.0 <2.8.12.8.1
GHSA-f4rr-5m7v-wxcwPyPItensorflow-gpu<2.6.42.6.4
GHSA-f4rr-5m7v-wxcwPyPItensorflow-gpu>=2.7.0 <2.7.22.7.2
GHSA-f4rr-5m7v-wxcwPyPItensorflow-gpu>=2.8.0 <2.8.12.8.1
PYSEC-2026-3167PyPItensorflow<2.6.4
>=2.7.0 <2.7.2
>=2.8.0 <2.8.1
2.6.4, 2.7.2, 2.8.1
PYSEC-2026-3315PyPItensorflow-cpu<2.6.4
>=2.7.0 <2.7.2
>=2.8.0 <2.8.1
2.6.4, 2.7.2, 2.8.1
PYSEC-2026-986PyPItensorflow-gpu<2.6.4
>=2.7.0 <2.7.2
>=2.8.0 <2.8.1
2.6.4, 2.7.2, 2.8.1

References

Check your stackJSON