Segmentation faultin TensorFlow when converting a Python string to `tf.float16` (CVE-2020-5215)

Segmentation faultin TensorFlow when converting a Python string to `tf.float16` (CVE-2020-5215) | HOL Guard CVE

Why this deserves its current priority

CVSS is 5.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps tensorflow (pypi), tensorflow (pypi), tensorflow-cpu (pypi), tensorflow-cpu (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
tensorflowpypi	>=0 <1.15.2	1.15.2
tensorflowpypi	>=2.0.0 <2.0.1	2.0.1
tensorflow-cpupypi	>=0 <1.15.2	1.15.2
tensorflow-cpupypi	>=2.0.0 <2.0.1	2.0.1
tensorflow-gpupypi	>=0 <1.15.2	1.15.2
tensorflow-gpupypi	>=2.0.0 <2.0.1	2.0.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for tensorflow, tensorflow, tensorflow-cpu.
Review the reported fix. Update tensorflow to 1.15.2; tensorflow to 2.0.1; tensorflow-cpu to 1.15.2; tensorflow-cpu to 2.0.1; tensorflow-gpu to 1.15.2; tensorflow-gpu to 2.0.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jan 28, 2020
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Impact Converting a string (from Python) to a `tf.float16` value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a `tf.float16` value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar `tf.float16` value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by `tf.constant("hello", tf.float16)`, if eager execution is enabled. ### Patches We have patched the vulnerability in GitHub commit [5ac1b9](https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf). We are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched. TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected. We encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0. ### For more information Please consult [`SECURITY.md`](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

Quoted source text, attributed separately from HOL analysis.