<?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-06T07:49:12.831297+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/cve-2020-15203</id>
    <title>CVE-2020-15203 — Denial of Service in Tensorflow</title>
    <updated>2026-10-06T07:49:12.833293+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> tensorflow</p>
<p>In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed. This may result in segmentation fault. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-15203"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xmq7-7fxm-rr79</id>
    <title>GHSA-xmq7-7fxm-rr79 — Denial of Service in Tensorflow</title>
    <updated>2026-10-06T07:49:12.833369+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
By controlling the `fill` argument of [`tf.strings.as_string`](https://www.tensorflow.org/api_docs/python/tf/strings/as_string), a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/as_string_op.cc#L68-L74</p>
<p>This can result in unexpected output:
```python
In [1]: tf.strings.as_string(input=[1234], width=6, fill='-')                                                                     
Out[1]: &lt;tf.Tensor: shape=(1,), dtype=string, numpy=array(['1234  '], dtype=object)&gt;                                              
In [2]: tf.strings.as_string(input=[1234], width=6, fill='+')                                                                     
Out[2]: &lt;tf.Tensor: shape=(1,), dtype=string, numpy=array([' +1234'], dtype=object)&gt; 
In [3]: tf.strings.as_string(input=[1234], width=6, fill="h")                                                                     
Out[3]: &lt;tf.Tensor: shape=(1,), dtype=string, numpy=array(['%6d'], dtype=object)&gt; 
In [4]: tf.strings.as_string(input=[1234], width=6, fill="d")                                                                     
Out[4]: &lt;tf.Tensor: shape=(1,), dtype=string, numpy=array(['12346d'], dtype=object)&gt; 
In [5]: tf.strings.as_string(input=[1234], width=6, fill="o")
Out[5]: &lt;tf.Tensor: shape=(1,), dtype=string, numpy=array([…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xmq7-7fxm-rr79"/>
  </entry>
</feed>
