<?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>Sun, 04 Oct 2026 13:30:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-15419</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-15419</link>
      <description>bdu:2026-15419</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-15419</guid>
    </item>
    <item>
      <title>BREW-aider-CVE-2026-73621 — GitPython: Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-73621</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;## Summary
`Commit.count()` forwards `**kwargs` into `rev_list` with **no** `check_unsafe_options` guard (the guard exists only in the sibling `iter_items`, commit.py:341). `git rev-list --output=&amp;lt;path&amp;gt;` opens and truncates the target file to 0 bytes before revision parsing, so `count(output=&amp;#39;/victim&amp;#39;)` destroys/blanks an arbitrary file.&lt;/p&gt;
&lt;p&gt;## Root Cause
`commit.py:290-291` calls `self.repo.git.rev_list(self.hexsha, **kwargs)` with no `check_unsafe_options` and no `allow_unsafe_options` parameter. The sibling `iter_items` (commit.py:341) is guarded; `count` is not. This is a distinct, uncovered sink — GHSA-956x-8gvw-wg5v fixed `iter_commits`/`blame`, not `count`.&lt;/p&gt;
&lt;p&gt;## Impact
Destroy/blank an arbitrary file at process privilege (integrity/availability). Reachability is key-control only (`count` uses `self.hexsha`, not a user ref), and the write is a 0-byte truncation (no content control), so MEDIUM.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
commit.count(output=&amp;#39;/path/to/victim&amp;#39;)   # victim truncated to 0 bytes (verified)
# control: commit.iter_commits(output=...) raises UnsafeOptionError
```&lt;/p&gt;
&lt;p&gt;## Attack Chain
1. Entry: app forwards user options -&amp;gt; `commit.count(output=&amp;#39;/victim&amp;#39;)`. Guard: none. Bypass proof: `iter_commits(output=)` raises UnsafeOptionError; `count(output=)` does not — verified side-by-side.
2. Sink: `git rev-list &amp;lt;sha&amp;gt; --output=/victim` -&amp;gt; file truncated to 0 bytes. Impact: destroy/blank arbitrary file.&lt;/p&gt;
&lt;p&gt;## Bypass Evidence
Live-verified on HEAD (tag 3.1.53): `count(output=&amp;lt;v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;## Summary
`Commit.count()` forwards `**kwargs` into `rev_list` with **no** `check_unsafe_options` guard (the guard exists only in the sibling `iter_items`, commit.py:341). `git rev-list --output=&amp;lt;path&amp;gt;` opens and truncates the target file to 0 bytes before revision parsing, so `count(output=&amp;#39;/victim&amp;#39;)` destroys/blanks an arbitrary file.&lt;/p&gt;
&lt;p&gt;## Root Cause
`commit.py:290-291` calls `self.repo.git.rev_list(self.hexsha, **kwargs)` with no `check_unsafe_options` and no `allow_unsafe_options` parameter. The sibling `iter_items` (commit.py:341) is guarded; `count` is not. This is a distinct, uncovered sink — GHSA-956x-8gvw-wg5v fixed `iter_commits`/`blame`, not `count`.&lt;/p&gt;
&lt;p&gt;## Impact
Destroy/blank an arbitrary file at process privilege (integrity/availability). Reachability is key-control only (`count` uses `self.hexsha`, not a user ref), and the write is a 0-byte truncation (no content control), so MEDIUM.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
commit.count(output=&amp;#39;/path/to/victim&amp;#39;)   # victim truncated to 0 bytes (verified)
# control: commit.iter_commits(output=...) raises UnsafeOptionError
```&lt;/p&gt;
&lt;p&gt;## Attack Chain
1. Entry: app forwards user options -&amp;gt; `commit.count(output=&amp;#39;/victim&amp;#39;)`. Guard: none. Bypass proof: `iter_commits(output=)` raises UnsafeOptionError; `count(output=)` does not — verified side-by-side.
2. Sink: `git rev-list &amp;lt;sha&amp;gt; --output=/victim` -&amp;gt; file truncated to 0 bytes. Impact: destroy/blank arbitrary file.&lt;/p&gt;
&lt;p&gt;## Bypass Evidence
Live-verified on HEAD (tag 3.1.53): `count(output=&amp;lt;v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-73621</guid>
    </item>
    <item>
      <title>EUVD-2026-352846</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-352846</link>
      <description>EUVD-2026-352846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-352846</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73621</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73621</link>
      <description>&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-73621</guid>
    </item>
    <item>
      <title>GHSA-h75v-4jxv-ppxm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h75v-4jxv-ppxm</link>
      <description>&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h75v-4jxv-ppxm</guid>
    </item>
    <item>
      <title>OESA-2026-3699 — python-GitPython security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3699</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: python-GitPython&lt;/p&gt;
&lt;p&gt;GitPython is a python library used to interact with git repositories, high-level like git-porcelain, or low-level like git-plumbing.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.(CVE-2026-73619)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.57 fails to guard git option forwarding in IndexFile.checkout() and TagReference.create(), allowing attackers to pass unsafe options via kwargs. Attackers can use --prefix to overwrite arbitrary files with repository content or -F to read arbitrary files returned in-band.(CVE-2026-73620)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;amp;apos;git rev-list&amp;amp;apos; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;amp;lt;path&amp;amp;gt;, causing &amp;amp;apos;git rev-list --output=&amp;amp;lt;path&amp;amp;gt;&amp;amp;apos; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;amp;apos;s privilege level (no content control, 0-byte truncation).(CVE-2026-73621)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.55 fails to disable env…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: python-GitPython&lt;/p&gt;
&lt;p&gt;GitPython is a python library used to interact with git repositories, high-level like git-porcelain, or low-level like git-plumbing.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.(CVE-2026-73619)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.57 fails to guard git option forwarding in IndexFile.checkout() and TagReference.create(), allowing attackers to pass unsafe options via kwargs. Attackers can use --prefix to overwrite arbitrary files with repository content or -F to read arbitrary files returned in-band.(CVE-2026-73620)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;amp;apos;git rev-list&amp;amp;apos; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;amp;lt;path&amp;amp;gt;, causing &amp;amp;apos;git rev-list --output=&amp;amp;lt;path&amp;amp;gt;&amp;amp;apos; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;amp;apos;s privilege level (no content control, 0-byte truncation).(CVE-2026-73621)&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.55 fails to disable env…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3699</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11566-1 — python313-GitPython-3.1.59-2.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11566-1</link>
      <description>&lt;p&gt;python313-GitPython-3.1.59-2.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python313-GitPython-3.1.59-2.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11566-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3950</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3950</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gitpython&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gitpython&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3950</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-73621</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73621</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: python-git, Ubuntu:Pro:16.04:LTS: python-git, Ubuntu:Pro:18.04:LTS: python-git, Ubuntu:Pro:20.04:LTS: python-git, Ubuntu:Pro:22.04:LTS: python-git, Ubuntu:Pro:24.04:LTS: python-git, Ubuntu:Pro:26.04:LTS: python-git&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: python-git, Ubuntu:Pro:16.04:LTS: python-git, Ubuntu:Pro:18.04:LTS: python-git, Ubuntu:Pro:20.04:LTS: python-git, Ubuntu:Pro:22.04:LTS: python-git, Ubuntu:Pro:24.04:LTS: python-git, Ubuntu:Pro:26.04:LTS: python-git&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to &amp;#39;git rev-list&amp;#39; without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=&amp;lt;path&amp;gt;, causing &amp;#39;git rev-list --output=&amp;lt;path&amp;gt;&amp;#39; to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process&amp;#39;s privilege level (no content control, 0-byte truncation).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73621</guid>
    </item>
  </channel>
</rss>
