cve.bz

CVE-2022-36015 google tensorflow: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.5 highEPSS 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.7.2, 2.8.1, 2.9.1.

On this page
TensorFlow is an open source platform for machine learning. When `RangeSize` receives values that do not fit into an `int64_t`, it crashes. We have patched the issue in GitHub commit 37e64539cd29fcfb814c4451152a60f5d107b0f0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

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.7% 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: 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-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
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-36015 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-36015?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-36015?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-36015 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.7.2
google:tensorflowfrom 2.8.0 before 2.8.1
google:tensorflowfrom 2.9.0 before 2.9.1
google:tensorflow2.10:rc0
google:tensorflow2.10:rc1
google:tensorflow2.10:rc2
google:tensorflow2.10:rc3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rh87-q4vg-m45jPyPItensorflow<2.7.22.7.2
GHSA-rh87-q4vg-m45jPyPItensorflow>=2.8.0 <2.8.12.8.1
GHSA-rh87-q4vg-m45jPyPItensorflow>=2.9.0 <2.9.12.9.1
GHSA-rh87-q4vg-m45jPyPItensorflow-cpu<2.7.22.7.2
GHSA-rh87-q4vg-m45jPyPItensorflow-cpu>=2.8.0 <2.8.12.8.1
GHSA-rh87-q4vg-m45jPyPItensorflow-cpu>=2.9.0 <2.9.12.9.1
GHSA-rh87-q4vg-m45jPyPItensorflow-gpu<2.7.22.7.2
GHSA-rh87-q4vg-m45jPyPItensorflow-gpu>=2.8.0 <2.8.12.8.1
GHSA-rh87-q4vg-m45jPyPItensorflow-gpu>=2.9.0 <2.9.12.9.1
PYSEC-2026-1033PyPItensorflow-gpu<2.7.2
>=2.8.0 <2.8.1
>=2.9.0 <2.9.1
2.7.2, 2.8.1, 2.9.1
PYSEC-2026-3237PyPItensorflow<2.7.2
>=2.8.0 <2.8.1
>=2.9.0 <2.9.1
2.7.2, 2.8.1, 2.9.1
PYSEC-2026-3367PyPItensorflow-cpu<2.7.2
>=2.8.0 <2.8.1
>=2.9.0 <2.9.1
2.7.2, 2.8.1, 2.9.1

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON