cve.bz

CVE-2022-41909 google tensorflow: NULL Pointer Dereference

7.5 highExploit referenceEPSS 0.7%Fix available

High (7.5) in google tensorflow. EPSS 0.7% 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. An input `encoded` that is not a valid `CompositeTensorVariant` tensor will trigger a segfault in `tf.raw_ops.CompositeTensorVariantToComponents`. We have patched the issue in GitHub commits bf594d08d377dc6a3354d9fdb494b32d45f91971 and 660ce5a89eb6766834bdc303d2ab3902aef99d3d. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 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.7% (unchanged from 0.7% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th 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.
CWEs
CWE-476 NULL Pointer Dereference
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection, A10:2025 Mishandling of Exceptional Conditions
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-41909 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-41909?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-41909?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-41909 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-rjx6-v474-2ch9PyPItensorflow<2.8.42.8.4
GHSA-rjx6-v474-2ch9PyPItensorflow>=2.9.0 <2.9.32.9.3
GHSA-rjx6-v474-2ch9PyPItensorflow>=2.10.0 <2.10.12.10.1
GHSA-rjx6-v474-2ch9PyPItensorflow-cpu<2.8.42.8.4
GHSA-rjx6-v474-2ch9PyPItensorflow-gpu<2.8.42.8.4
GHSA-rjx6-v474-2ch9PyPItensorflow-cpu>=2.9.0 <2.9.32.9.3
GHSA-rjx6-v474-2ch9PyPItensorflow-gpu>=2.9.0 <2.9.32.9.3
GHSA-rjx6-v474-2ch9PyPItensorflow-cpu>=2.10.0 <2.10.12.10.1
GHSA-rjx6-v474-2ch9PyPItensorflow-gpu>=2.10.0 <2.10.12.10.1
PYSEC-2026-1034PyPItensorflow-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-3238PyPItensorflow<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-3368PyPItensorflow-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-11543

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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON