<?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>Wed, 30 Sep 2026 03:09:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55621 — Incus has a project restriction bypass for custom volume copy across projects</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-55621</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, missing authorization checks exist for custom volume copying where an attacker knowing the name of a project that they don&amp;#39;t have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access. 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, missing authorization checks exist for custom volume copying where an attacker knowing the name of a project that they don&amp;#39;t have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access. Version 7.2.0 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-55621</guid>
    </item>
    <item>
      <title>GHSA-64f3-v33m-w89f — Incus has a project restriction bypass for custom volume copy across projects</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-64f3-v33m-w89f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lxc/incus/v7, Go: github.com/lxc/incus/v6, Go: github.com/lxc/incus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Missing authorization checks exist for custom volume copying where an attacker who knows the name of a project that they don&amp;#39;t have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The storage volume creation handler authorizes creation in the target project, then passes `req.Source.Project` into the custom-volume copy path without checking that the caller can view the source volume. `req.Source.Project` is the attacker-controlled field. It is resolved to a storage volume project name and passed directly to `CreateCustomVolumeFromCopy`. No `allowPermission` or entitlement check (e.g. `CanView` on the source volume) is performed.&lt;/p&gt;
&lt;p&gt;The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the volume to another server.&lt;/p&gt;
&lt;p&gt;### PoC
#### Setup&lt;/p&gt;
&lt;p&gt;Assume the target server is remotely accessible and a user/certificate has been added.&lt;/p&gt;
&lt;p&gt;```
# create a new project and instance
incus project create secrets
incus profile show default | incus --project secrets edit default
incus --project secrets storage volume create default secret-vol&lt;/p&gt;
&lt;p&gt;# restrict an existing certificate to prevent access to the project
incus config trust edit cert-fp
#&amp;gt; set, for example
restricted: true
projects:
  - default&lt;/p&gt;
&lt;p&gt;# verification, with the restricted certificate
i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lxc/incus/v7, Go: github.com/lxc/incus/v6, Go: github.com/lxc/incus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Missing authorization checks exist for custom volume copying where an attacker who knows the name of a project that they don&amp;#39;t have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The storage volume creation handler authorizes creation in the target project, then passes `req.Source.Project` into the custom-volume copy path without checking that the caller can view the source volume. `req.Source.Project` is the attacker-controlled field. It is resolved to a storage volume project name and passed directly to `CreateCustomVolumeFromCopy`. No `allowPermission` or entitlement check (e.g. `CanView` on the source volume) is performed.&lt;/p&gt;
&lt;p&gt;The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the volume to another server.&lt;/p&gt;
&lt;p&gt;### PoC
#### Setup&lt;/p&gt;
&lt;p&gt;Assume the target server is remotely accessible and a user/certificate has been added.&lt;/p&gt;
&lt;p&gt;```
# create a new project and instance
incus project create secrets
incus profile show default | incus --project secrets edit default
incus --project secrets storage volume create default secret-vol&lt;/p&gt;
&lt;p&gt;# restrict an existing certificate to prevent access to the project
incus config trust edit cert-fp
#&amp;gt; set, for example
restricted: true
projects:
  - default&lt;/p&gt;
&lt;p&gt;# verification, with the restricted certificate
i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-64f3-v33m-w89f</guid>
    </item>
  </channel>
</rss>
