<?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>Tue, 29 Sep 2026 07:05:35 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-82253</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-82253</link>
      <description>&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-82253</guid>
    </item>
    <item>
      <title>GHSA-6f8q-f8px-cxhw</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6f8q-f8px-cxhw</link>
      <description>&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6f8q-f8px-cxhw</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-82253 — gitoxide before 0.82.0 Path Traversal via Submodule Name Validation Bypass</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-82253</link>
      <description>msrc_CVE-2026-82253</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-82253</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11730-1 — cargo-audit-0.22.2~git0.281452c-3.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11730-1</link>
      <description>&lt;p&gt;cargo-audit-0.22.2~git0.281452c-3.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cargo-audit-0.22.2~git0.281452c-3.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11730-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-82253</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-82253</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: rust-gix-validate, Ubuntu:26.04:LTS: rust-gix, Ubuntu:26.04:LTS: rust-gix-validate&lt;/p&gt;
&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: rust-gix-validate, Ubuntu:26.04:LTS: rust-gix, Ubuntu:26.04:LTS: rust-gix-validate&lt;/p&gt;
&lt;p&gt;gitoxide (Rust crates gix &amp;lt;= 0.72.0 and gix-validate &amp;lt;= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of &amp;#39;..&amp;#39; via name.find(b&amp;#34;..&amp;#34;), allowing crafted names such as &amp;#39;a..b/../../../.git/&amp;#39; to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository&amp;#39;s git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-82253</guid>
    </item>
  </channel>
</rss>
