<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T03:15:16.657111+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/rustsec-2025-0020</id>
    <title>RUSTSEC-2025-0020 — Risk of buffer overflow in `PyString::from_object`</title>
    <updated>2026-11-22T03:15:16.658613+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: pyo3</p>
<p>`PyString::from_object` took `&amp;str` arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the `&amp;str` data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow).</p>
<p>In PyO3 0.24.1 this function will now allocate a `CString` to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes `&amp;CStr` arguments.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/rustsec-2025-0020"/>
  </entry>
</feed>
