<?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-08T14:54:11.395839+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/bdu:2021-03533</id>
    <title>bdu:2021-03533</title>
    <updated>2026-10-08T14:54:11.399539+00:00</updated>
    <content>bdu:2021-03533</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2021-03533"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-58455</id>
    <title>EUVD-2026-58455</title>
    <updated>2026-10-08T14:54:11.399574+00:00</updated>
    <content>EUVD-2026-58455</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-58455"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2019-17514</id>
    <title>fkie_cve-2019-17514</title>
    <updated>2026-10-08T14:54:11.399589+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated "finds all the pathnames matching a specified pattern according to the rules used by the Unix shell," one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2019-17514"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pgrc-mvjg-qfr7</id>
    <title>GHSA-pgrc-mvjg-qfr7</title>
    <updated>2026-10-08T14:54:11.399623+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated "finds all the pathnames matching a specified pattern according to the rules used by the Unix shell," one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pgrc-mvjg-qfr7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2019-17514</id>
    <title>gsd-2019-17514</title>
    <updated>2026-10-08T14:54:11.399644+00:00</updated>
    <content>gsd-2019-17514</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2019-17514"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-17514</id>
    <title>UBUNTU-CVE-2019-17514</title>
    <updated>2026-10-08T14:54:11.399655+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: python2.7, Ubuntu:Pro:14.04:LTS: python3.4, Ubuntu:Pro:14.04:LTS: python3.5, Ubuntu:16.04:LTS: python2.7, Ubuntu:16.04:LTS: python3.5, Ubuntu:18.04:LTS: python2.7, Ubuntu:18.04:LTS: python3.6, Ubuntu:18.04:LTS: python3.8, Ubuntu:Pro:18.04:LTS: python3.7, Ubuntu:20.04:LTS: python2.7 and 2 more</p>
<p>library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated "finds all the pathnames matching a specified pattern according to the rules used by the Unix shell," one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-17514"/>
  </entry>
</feed>
