<?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://db.gcve.eu</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, 11 Nov 2026 07:15:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-62268</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-62268</link>
      <description>&lt;p&gt;borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption. Prior to 1.4.5 and 2.0.0b22, extracting a malicious archive can follow a symlinked parent path or resolve embedded dot-dot path components and delete or overwrite files outside the extraction directory. A crafted slave hardlink can also use an attacker-controlled hardlink source outside the extraction directory and hard-link that file into the restored tree, disclosing its contents. Creating the malicious archive requires repository access and, for encrypted or authenticated repositories, the Borg key and passphrase; a victim must then extract the archive. This issue is fixed in versions 1.4.5 and 2.0.0b22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption. Prior to 1.4.5 and 2.0.0b22, extracting a malicious archive can follow a symlinked parent path or resolve embedded dot-dot path components and delete or overwrite files outside the extraction directory. A crafted slave hardlink can also use an attacker-controlled hardlink source outside the extraction directory and hard-link that file into the restored tree, disclosing its contents. Creating the malicious archive requires repository access and, for encrypted or authenticated repositories, the Borg key and passphrase; a victim must then extract the archive. This issue is fixed in versions 1.4.5 and 2.0.0b22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-62268</guid>
    </item>
    <item>
      <title>GHSA-gfp8-w835-v44j — borg extract might modify out-of-tree files when extracting maliciously crafted archives</title>
      <link>https://db.gcve.eu/vuln/ghsa-gfp8-w835-v44j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: borgbackup&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A maliciously crafted archive could contain a symlink (e.g. &amp;#34;evil&amp;#34; -&amp;gt; &amp;#34;/etc&amp;#34;) followed by an item below it (&amp;#34;evil/passwd&amp;#34;), or an item whose path embeds &amp;#34;..&amp;#34; (e.g. &amp;#34;a/../../etc/passwd&amp;#34;).&lt;/p&gt;
&lt;p&gt;When extracting such items, borg followed the symlink / resolved the &amp;#34;..&amp;#34;, so it could delete or overwrite files outside the extraction directory.&lt;/p&gt;
&lt;p&gt;In a quite similar scenario, a crafted archive could contain a slave hardlink item with the hardlink source pointing outside the extraction directory.&lt;/p&gt;
&lt;p&gt;When extracting such an item, borg would hard-link the outside and the inside item.
    
Note: that sounds bad, but it is no big issue in practice: to create such a malicious archive, the attacker would need repository access and (for encrypted or authenticated repos) also the borg key and passphrase.&lt;/p&gt;
&lt;p&gt;Affected: likely all borg releases before 1.4.5 (and also all borg 2.0.0 betas before b22).&lt;/p&gt;
&lt;p&gt;### Patches
- 1.4.x release series: fix released with 1.4.5. commits 3e9ed6d1ad6d3531b39c07b8ef3ecf41fce4437f and 141888f2fabcd57a300547c2aa63212cb213924d.
- 1.2.x release series: no new releases any more, fix commits available on 1.2-maint branch: 0ac568e290518c3bbe781459978720dde7fab224 and d907f2cb57337041c4fa55ca4682895535e5076b
- 2.0.0 betas: fix will be in 2.0.0b22, fix commits on master branch: 2d632531028b09da8ab5d1450f89bebcc205d640 and 4f37fdfed10b50559a0dd333b0d5581c642af329&lt;/p&gt;
&lt;p&gt;### Workarounds
For encrypted or authenticated repositories, do not share borg key and passphrase with potenti…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: borgbackup&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A maliciously crafted archive could contain a symlink (e.g. &amp;#34;evil&amp;#34; -&amp;gt; &amp;#34;/etc&amp;#34;) followed by an item below it (&amp;#34;evil/passwd&amp;#34;), or an item whose path embeds &amp;#34;..&amp;#34; (e.g. &amp;#34;a/../../etc/passwd&amp;#34;).&lt;/p&gt;
&lt;p&gt;When extracting such items, borg followed the symlink / resolved the &amp;#34;..&amp;#34;, so it could delete or overwrite files outside the extraction directory.&lt;/p&gt;
&lt;p&gt;In a quite similar scenario, a crafted archive could contain a slave hardlink item with the hardlink source pointing outside the extraction directory.&lt;/p&gt;
&lt;p&gt;When extracting such an item, borg would hard-link the outside and the inside item.
    
Note: that sounds bad, but it is no big issue in practice: to create such a malicious archive, the attacker would need repository access and (for encrypted or authenticated repos) also the borg key and passphrase.&lt;/p&gt;
&lt;p&gt;Affected: likely all borg releases before 1.4.5 (and also all borg 2.0.0 betas before b22).&lt;/p&gt;
&lt;p&gt;### Patches
- 1.4.x release series: fix released with 1.4.5. commits 3e9ed6d1ad6d3531b39c07b8ef3ecf41fce4437f and 141888f2fabcd57a300547c2aa63212cb213924d.
- 1.2.x release series: no new releases any more, fix commits available on 1.2-maint branch: 0ac568e290518c3bbe781459978720dde7fab224 and d907f2cb57337041c4fa55ca4682895535e5076b
- 2.0.0 betas: fix will be in 2.0.0b22, fix commits on master branch: 2d632531028b09da8ab5d1450f89bebcc205d640 and 4f37fdfed10b50559a0dd333b0d5581c642af329&lt;/p&gt;
&lt;p&gt;### Workarounds
For encrypted or authenticated repositories, do not share borg key and passphrase with potenti…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gfp8-w835-v44j</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-62268</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-62268</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: borgbackup, Ubuntu:18.04:LTS: borgbackup, Ubuntu:20.04:LTS: borgbackup, Ubuntu:22.04:LTS: borgbackup, Ubuntu:24.04:LTS: borgbackup, Ubuntu:24.04:LTS: borgbackup2, Ubuntu:26.10: borgbackup, Ubuntu:26.10: borgbackup2, Ubuntu:26.04:LTS: borgbackup, Ubuntu:26.04:LTS: borgbackup2&lt;/p&gt;
&lt;p&gt;[Unknown description]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: borgbackup, Ubuntu:18.04:LTS: borgbackup, Ubuntu:20.04:LTS: borgbackup, Ubuntu:22.04:LTS: borgbackup, Ubuntu:24.04:LTS: borgbackup, Ubuntu:24.04:LTS: borgbackup2, Ubuntu:26.10: borgbackup, Ubuntu:26.10: borgbackup2, Ubuntu:26.04:LTS: borgbackup, Ubuntu:26.04:LTS: borgbackup2&lt;/p&gt;
&lt;p&gt;[Unknown description]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-62268</guid>
    </item>
  </channel>
</rss>
