<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T13:10:35.702019+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/rustsec-2022-0051</id>
    <title>RUSTSEC-2022-0051 — Memory corruption in liblz4</title>
    <updated>2026-10-07T13:10:35.722066+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: lz4-sys</p>
<p>lz4-sys up to v1.9.3 bundles a version of liblz4 that is vulnerable to
[CVE-2021-3520](https://nvd.nist.gov/vuln/detail/CVE-2021-3520).</p>
<p>Attackers could craft a payload that triggers an integer overflow upon
decompression, causing an out-of-bounds write.</p>
<p>The flaw has been corrected in version v1.9.4 of liblz4, which is included
in lz4-sys 1.9.4.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rustsec-2022-0051"/>
  </entry>
</feed>
