<?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-09-30T01:58:30.481730+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/cve-2020-27348</id>
    <title>CVE-2020-27348 — snapcraft may build snaps with incorrect LD_LIBRARY_PATH</title>
    <updated>2026-09-30T01:58:30.522690+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Canonical snapcraft</p>
<p>In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43.1+16.04.1, and prior to 2.43.1+18.04.1.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2020-27348"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-4661-1</id>
    <title>USN-4661-1 — snapcraft vulnerability</title>
    <updated>2026-09-30T01:58:30.522792+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: snapcraft, Ubuntu:18.04:LTS: snapcraft</p>
<p>It was discovered that Snapcraft includes the current directory when
configuring LD_LIBRARY_PATH for application commands. If a user were
tricked into installing a malicious snap or downloading a malicious
library, under certain circumstances an attacker could exploit this to
affect strict mode snaps that have access to the library and when
launched from the directory containing the library.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-4661-1"/>
  </entry>
</feed>
