<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 07:37:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-15226 — snapd snap-confine Sandbox Confinement Bypass via Omission of setuid Restriction in Seccomp Templates</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-15226</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; snapd, Canonical Ubuntu 26.04 LTS, Canonical Ubuntu 24.04 LTS, Canonical Ubuntu 22.04 LTS, Canonical Ubuntu 20.04 LTS, Canonical Ubuntu 18.04 LTS, Canonical Ubuntu 16.04 LTS&lt;/p&gt;
&lt;p&gt;A sandbox confinement bypass vulnerability exists in Canonical snapd within its internal execution environment compiler (snap-confine). The default seccomp security templates generated by the engine to restrict system calls do not filter or reject process operations capable of creating or manipulating file execution flags with set-user-ID attributes.  Consequently, an application running within a strictly confined snap environment can successfully compile or drop binaries and apply setuid properties to them. If a compromised or malicious process inside the snap sandbox executes these generated setuid binaries, it can potentially circumvent architectural sandboxing assumptions, drop intended restriction policies, or execute privileged actions inside the container namespace that should otherwise be strictly blocked. The vulnerability has been resolved by hardening the seccomp template engine to block the execution and creation of setuid executables by sandboxed snap processes.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; snapd, Canonical Ubuntu 26.04 LTS, Canonical Ubuntu 24.04 LTS, Canonical Ubuntu 22.04 LTS, Canonical Ubuntu 20.04 LTS, Canonical Ubuntu 18.04 LTS, Canonical Ubuntu 16.04 LTS&lt;/p&gt;
&lt;p&gt;A sandbox confinement bypass vulnerability exists in Canonical snapd within its internal execution environment compiler (snap-confine). The default seccomp security templates generated by the engine to restrict system calls do not filter or reject process operations capable of creating or manipulating file execution flags with set-user-ID attributes.  Consequently, an application running within a strictly confined snap environment can successfully compile or drop binaries and apply setuid properties to them. If a compromised or malicious process inside the snap sandbox executes these generated setuid binaries, it can potentially circumvent architectural sandboxing assumptions, drop intended restriction policies, or execute privileged actions inside the container namespace that should otherwise be strictly blocked. The vulnerability has been resolved by hardening the seccomp template engine to block the execution and creation of setuid executables by sandboxed snap processes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-15226</guid>
    </item>
  </channel>
</rss>
