CVE-2018-7576: Null Pointer Dereference in Google TensorFlow 1.6.x and earlier

tensorflow-gpu Updated 02 Oct 2025

Summary

23/04/2019
Yes i
Unrated
Not published

CVE-2018-7576: Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent. Affects tensorflow-gpu versions < 1.7.0rc0. Fixed in 1.7.0rc0. How to fix ↓

Also tracked for

The same CVE-2018-7576 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 and deploying machine learning models. TensorFlow 1.6.x and earlier versions are impacted by a Null Pointer Dereference vulnerability.

Vulnerability Detail

The vulnerability in TensorFlow 1.6.x and earlier versions is a Null Pointer Dereference issue. This type of vulnerability occurs when a program attempts to access or dereference a null pointer, resulting in a crash or unexpected behavior. An attacker could potentially exploit this vulnerability in a context-dependent manner, leading to a denial of service or the execution of arbitrary code. It is crucial to address this vulnerability to prevent potential system compromise or disruption.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-gpu==2.12.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.0rc0

This is the first release that contains the fix.

pip install --upgrade "tensorflow-gpu==1.7.0rc0"

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

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the fixed version of TensorFlow.

Conclusion

In conclusion, the Null Pointer Dereference vulnerability in Google TensorFlow 1.6.x and earlier versions poses a risk of system compromise or disruption. It is crucial to upgrade to TensorFlow version 1.7.0rc0 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow-gpu →

Share this vulnerability

FAQ

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

A Null Pointer Dereference vulnerability occurs when a program attempts to access or dereference a null pointer, resulting in a crash or unexpected behavior.

The vulnerability could lead to a denial of service or the execution of arbitrary code, potentially compromising the system or causing disruption.

To fix the vulnerability, it is recommended to upgrade to TensorFlow version 1.7.0rc0 or later.

There is no specific workaround mentioned for this vulnerability. Upgrading to the fixed version is the recommended approach.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow-gpu.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-gpu==2.12.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.0rc0

This is the first release that contains the fix.

pip install --upgrade "tensorflow-gpu==1.7.0rc0"

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