cve.bz

CVE-2023-25668 google tensorflow: Heap-based Buffer Overflow

9.8 criticalExploit referenceEPSS 0.8%Fix available

Critical (9.8) in google tensorflow. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.11.1.

On this page
TensorFlow is an open source platform for machine learning. Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution. The fix will be included in TensorFlow version 2.12.0 and will also cherrypick this commit on TensorFlow version 2.11.1.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th 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: yes · Technical impact: total, assessed 2025-02-19. 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-122 Heap-based Buffer Overflow
CWE-125 Out-of-bounds Read
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-2023-25668 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-25668?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-25668?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-2023-25668 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.12.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gw97-ff7c-9v96PyPItensorflow<2.11.12.11.1
GHSA-gw97-ff7c-9v96PyPItensorflow-cpu<2.11.12.11.1
GHSA-gw97-ff7c-9v96PyPItensorflow-gpu<2.11.12.11.1
PYSEC-2026-548PyPItensorflow<2.11.12.11.1
PYSEC-2026-549PyPItensorflow-cpu<2.11.12.11.1
PYSEC-2026-550PyPItensorflow-gpu<2.11.12.11.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux2tensorflow2.11.1-1AZL-31200
Azure Linux3tensorflow2.11.1-1AZL-35313

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)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High
  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

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

References

Check your stackJSON