<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T07:03:29.367553+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-tensorflow-2020-5215</id>
    <title>BIT-tensorflow-2020-5215 — Segmentation faultin TensorFlow when converting a Python string to tf.float16</title>
    <updated>2026-10-09T07:03:29.372762+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: tensorflow</p>
<p>In TensorFlow before 1.15.2 and 2.0.1, 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. This issue is patched in 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. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-tensorflow-2020-5215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2020-04913</id>
    <title>cnvd-2020-04913</title>
    <updated>2026-10-09T07:03:29.372817+00:00</updated>
    <content>cnvd-2020-04913</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2020-04913"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-36465</id>
    <title>EUVD-2026-36465</title>
    <updated>2026-10-09T07:03:29.372835+00:00</updated>
    <content>EUVD-2026-36465</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-36465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-5215</id>
    <title>fkie_cve-2020-5215</title>
    <updated>2026-10-09T07:03:29.372847+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In TensorFlow before 1.15.2 and 2.0.1, 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. This issue is patched in 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. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-5215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-977j-xj7q-2jr9</id>
    <title>GHSA-977j-xj7q-2jr9 — Segmentation faultin TensorFlow when converting a Python string to `tf.float16`</title>
    <updated>2026-10-09T07:03:29.372874+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu</p>
<p>### Impact</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>This can be easily reproduced by `tf.constant("hello", tf.float16)`, if eager execution is enabled.</p>
<p>### Patches
We have patched the vulnerability in GitHub commit [5ac1b9](https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf).</p>
<p>We are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched.</p>
<p>TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected.</p>
<p>We encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.</p>
<p>### For more information</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-977j-xj7q-2jr9"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-5215</id>
    <title>gsd-2020-5215</title>
    <updated>2026-10-09T07:03:29.372912+00:00</updated>
    <content>gsd-2020-5215</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-5215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2020-258</id>
    <title>PYSEC-2020-258</title>
    <updated>2026-10-09T07:03:29.372923+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: tensorflow</p>
<p>In TensorFlow before 1.15.2 and 2.0.1, 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. This issue is patched in 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. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2020-258"/>
  </entry>
</feed>
