<?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-07T23:06:21.044104+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-2021-45703</id>
    <title>CVE-2021-45703</title>
    <updated>2026-10-07T23:06:21.046029+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the tectonic_xdv crate before 0.1.12 for Rust. XdvParser::&lt;T&gt;::process may read from uninitialized memory locations.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-45703"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6692-8qqf-79jc</id>
    <title>Withdrawn: GHSA-6692-8qqf-79jc — Duplicate Advisory: `Read` on uninitialized buffer may cause UB ('tectonic_xdv' crate)</title>
    <updated>2026-10-07T23:06:21.046077+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> crates.io: tectonic_xdv</p>
<p>## Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-qwvx-c8j7-5g75. This link is maintained to preserve external references.</p>
<p>## Original Description
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.</p>
<p>Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.</p>
<p>The problem was fixed in commit `cdff034` by zero-initializing the buffer before passing it to a user-provided `Read` implementation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6692-8qqf-79jc"/>
  </entry>
</feed>
