<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 10:03:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23986 — Copier safe template has arbitrary filesystem write access via directory symlinks when _preserve_symlinks: true</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-23986</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; copier-org copier&lt;/p&gt;
&lt;p&gt;Copier is a library and CLI app for rendering project templates. Prior to version 9.11.2, Copier suggests that it&amp;#39;s safe to generate a project from a safe template, i.e. one that doesn&amp;#39;t use unsafe features like custom Jinja extensions which would require passing the `--UNSAFE,--trust` flag. As it turns out, a safe template can currently write to arbitrary directories outside the destination path by using directory a symlink along with `_preserve_symlinks: true` and a generated directory structure whose rendered path is inside the symlinked directory. This way, a malicious template author can create a template that overwrites arbitrary files (according to the user&amp;#39;s write permissions), e.g., to cause havoc. Version 9.11.2 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; copier-org copier&lt;/p&gt;
&lt;p&gt;Copier is a library and CLI app for rendering project templates. Prior to version 9.11.2, Copier suggests that it&amp;#39;s safe to generate a project from a safe template, i.e. one that doesn&amp;#39;t use unsafe features like custom Jinja extensions which would require passing the `--UNSAFE,--trust` flag. As it turns out, a safe template can currently write to arbitrary directories outside the destination path by using directory a symlink along with `_preserve_symlinks: true` and a generated directory structure whose rendered path is inside the symlinked directory. This way, a malicious template author can create a template that overwrites arbitrary files (according to the user&amp;#39;s write permissions), e.g., to cause havoc. Version 9.11.2 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-23986</guid>
    </item>
  </channel>
</rss>
