<?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-14T19:38:03.871458+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/rustsec-2026-0013</id>
    <title>RUSTSEC-2026-0013 — Type confusion when accessing data from sublasses of subclasses of native types with `abi3` feature targeting Python 3.…</title>
    <updated>2026-10-14T19:38:03.898219+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: pyo3</p>
<p>PyO3 0.28.1 added support for `#[pyclass(extends=PyList)] struct NativeSub` (and other native types) when targeting Python 3.12 and up with the `abi3` feature.</p>
<p>It was discovered that subclasses of such classes would use the type of the subclass when attempting to access to data of `NativeSub` contained within Python objects, amounting to memory corruption.</p>
<p>PyO3 0.28.2 fixed the issue by using the type of (e.g.) `NativeSub` correctly.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2026-0013"/>
  </entry>
</feed>
