Advisory record · GHSA-977j-xj7q-2jr9

Segmentation faultin TensorFlow when converting a Python string to `tf.float16`

CVSS 5.0 MediumEPSS 0.0059 · 48th percentile

Published by the GitHub Advisory Database at 28 Jan 2020, 21:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tensorflowPyPI<1.15.2 || >=2.0.0, <2.0.11.15.2, 2.0.1
tensorflow-cpuPyPI<1.15.2 || >=2.0.0, <2.0.11.15.2, 2.0.1
tensorflow-gpuPyPI<1.15.2 || >=2.0.0, <2.0.11.15.2, 2.0.1
Identifiers
GHSA-977j-xj7q-2jr9 · BIT-tensorflow-2020-5215 · CVE-2020-5215 · PYSEC-2020-258 · PYSEC-2020-303 · PYSEC-2020-338
Weakness (CWE)
CWE-754
Published
28 Jan 2020
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The tensorflow, tensorflow-cpu and tensorflow-gpu packages, versions below 1.15.2 and version 2.0.0, segfault when a Python string is converted to tf.float16 in eager mode. An attacker who supplies a string instead of a float16 value in input data or a saved model can cause a denial of service. Upgrade to 1.15.2 or 2.0.1.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.0 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0059, the 48th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:38 UTC First seen by agentprime
  2. 31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.