CVE-2018-7575: Buffer Overflow in Google TensorFlow

tensorflow Updated 02 Oct 2025

Summary

24/04/2019
Yes i
Critical
9.8

CVE-2018-7575: Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. Affects tensorflow versions < 1.7.1. Fixed in 1.7.1. How to fix ↓

Also tracked for

The same CVE-2018-7575 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Google TensorFlow is an open-source machine learning framework used for building and training neural networks. It provides a comprehensive ecosystem of tools, libraries, and resources for developing AI applications. TensorFlow versions 1.7.x and earlier are affected by a Buffer Overflow vulnerability. This vulnerability can be exploited in various contexts, leading to potential security breaches.

Vulnerability Detail

The Buffer Overflow vulnerability in Google TensorFlow arises due to improper handling of input data. An attacker can craft malicious input that exceeds the bounds of a buffer, causing the program to overwrite adjacent memory. This can result in the execution of arbitrary code or a system crash, potentially leading to remote code execution or denial of service attacks. The vulnerability affects versions 1.7.x and earlier of TensorFlow.

How To Fix

Latest published version: 2.21.0 as of 22 Oct 2026

pip install --upgrade "tensorflow==2.21.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.7.1

This is the first release that contains the fix.

pip install --upgrade "tensorflow==1.7.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to the fixed version of TensorFlow to ensure the security of your system.

Conclusion

The Buffer Overflow vulnerability in Google TensorFlow can have severe security implications, including remote code execution and denial of service attacks. It is crucial to update to TensorFlow version 1.7.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open-source machine learning framework developed by Google. It provides a platform for building and training neural networks.

A Buffer Overflow vulnerability occurs when a program writes data beyond the boundaries of a buffer, leading to memory corruption and potential security exploits.

This vulnerability can be exploited by crafting malicious input that exceeds the bounds of a buffer, causing adjacent memory to be overwritten. This can lead to arbitrary code execution or system crashes.

Versions 1.7.x and earlier of TensorFlow are affected by this vulnerability.

Yes, upgrading to TensorFlow version 1.7.1 or later will fix this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow.

How To Fix

Latest published version: 2.21.0 as of 22 Oct 2026

pip install --upgrade "tensorflow==2.21.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.7.1

This is the first release that contains the fix.

pip install --upgrade "tensorflow==1.7.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback