<?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>Fri, 02 Oct 2026 10:55:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12784</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12784</link>
      <description>bdu:2026-12784</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12784</guid>
    </item>
    <item>
      <title>BREW-aider-CVE-2026-78678 — GitPython: Incomplete unsafe_git_revision_options denylist omits --contents/-S, enabling arbitrary file read via Repo.b…</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-78678</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;## Summary
`Repo.blame()` / `Repo.blame_incremental()` guard forwarded revision options against `unsafe_git_revision_options`, but that denylist only contains the file-WRITE options `--output`/`-o`. `git blame` also honors `--contents &amp;lt;file&amp;gt;` and `-S &amp;lt;file&amp;gt;`, which cause the file&amp;#39;s lines to be echoed into the blame result — an arbitrary file READ. Neither option is in the denylist, so a caller-influenced revision value of `--contents=&amp;lt;path&amp;gt;` passes the guard and leaks file contents. This is a distinct sink-option and impact class (READ) from GHSA-956x-8gvw-wg5v (which addressed the blame `--output` WRITE), directly analogous to GHSA-539m-9xh6-q6rr (archive READ gap accepted separately from the archive write/exec advisory).&lt;/p&gt;
&lt;p&gt;## Root Cause
`unsafe_git_revision_options = [&amp;#34;--output&amp;#34;,&amp;#34;-o&amp;#34;]` (`git/repo/base.py:188`). The `rev` string is passed to `_option_candidates([rev], kwargs)` and placed BEFORE the `--` separator (base.py:841). The canonical name of `--contents=...` is `contents`, which is not on the denylist, so no `UnsafeOptionError` is raised. The trailing `--` protects only the pathspec, not the option before the revision.&lt;/p&gt;
&lt;p&gt;## Impact
Arbitrary local file read at the privileges of the host process; the file&amp;#39;s line contents appear in the blame result returned to the caller. Pure VALUE control (the caller forwards a user-influenced revision string). Default `allow_unsafe_options=False`.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
result = repo.blame(&amp;#34;--contents=/etc/passwd&amp;#34;, &amp;#34;a.txt&amp;#34;)
#…&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
`Repo.blame()` / `Repo.blame_incremental()` guard forwarded revision options against `unsafe_git_revision_options`, but that denylist only contains the file-WRITE options `--output`/`-o`. `git blame` also honors `--contents &amp;lt;file&amp;gt;` and `-S &amp;lt;file&amp;gt;`, which cause the file&amp;#39;s lines to be echoed into the blame result — an arbitrary file READ. Neither option is in the denylist, so a caller-influenced revision value of `--contents=&amp;lt;path&amp;gt;` passes the guard and leaks file contents. This is a distinct sink-option and impact class (READ) from GHSA-956x-8gvw-wg5v (which addressed the blame `--output` WRITE), directly analogous to GHSA-539m-9xh6-q6rr (archive READ gap accepted separately from the archive write/exec advisory).&lt;/p&gt;
&lt;p&gt;## Root Cause
`unsafe_git_revision_options = [&amp;#34;--output&amp;#34;,&amp;#34;-o&amp;#34;]` (`git/repo/base.py:188`). The `rev` string is passed to `_option_candidates([rev], kwargs)` and placed BEFORE the `--` separator (base.py:841). The canonical name of `--contents=...` is `contents`, which is not on the denylist, so no `UnsafeOptionError` is raised. The trailing `--` protects only the pathspec, not the option before the revision.&lt;/p&gt;
&lt;p&gt;## Impact
Arbitrary local file read at the privileges of the host process; the file&amp;#39;s line contents appear in the blame result returned to the caller. Pure VALUE control (the caller forwards a user-influenced revision string). Default `allow_unsafe_options=False`.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
result = repo.blame(&amp;#34;--contents=/etc/passwd&amp;#34;, &amp;#34;a.txt&amp;#34;)
#…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-78678</guid>
    </item>
    <item>
      <title>EUVD-2026-358785</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358785</link>
      <description>EUVD-2026-358785</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358785</guid>
    </item>
    <item>
      <title>fkie_cve-2026-78678</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78678</link>
      <description>&lt;p&gt;GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-78678</guid>
    </item>
    <item>
      <title>GHSA-5xxx-qhh7-9287 — GitPython: Incomplete unsafe_git_revision_options denylist omits --contents/-S, enabling arbitrary file read via Repo.b…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xxx-qhh7-9287</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: GitPython&lt;/p&gt;
&lt;p&gt;## Summary
`Repo.blame()` / `Repo.blame_incremental()` guard forwarded revision options against `unsafe_git_revision_options`, but that denylist only contains the file-WRITE options `--output`/`-o`. `git blame` also honors `--contents &amp;lt;file&amp;gt;` and `-S &amp;lt;file&amp;gt;`, which cause the file&amp;#39;s lines to be echoed into the blame result — an arbitrary file READ. Neither option is in the denylist, so a caller-influenced revision value of `--contents=&amp;lt;path&amp;gt;` passes the guard and leaks file contents. This is a distinct sink-option and impact class (READ) from GHSA-956x-8gvw-wg5v (which addressed the blame `--output` WRITE), directly analogous to GHSA-539m-9xh6-q6rr (archive READ gap accepted separately from the archive write/exec advisory).&lt;/p&gt;
&lt;p&gt;## Root Cause
`unsafe_git_revision_options = [&amp;#34;--output&amp;#34;,&amp;#34;-o&amp;#34;]` (`git/repo/base.py:188`). The `rev` string is passed to `_option_candidates([rev], kwargs)` and placed BEFORE the `--` separator (base.py:841). The canonical name of `--contents=...` is `contents`, which is not on the denylist, so no `UnsafeOptionError` is raised. The trailing `--` protects only the pathspec, not the option before the revision.&lt;/p&gt;
&lt;p&gt;## Impact
Arbitrary local file read at the privileges of the host process; the file&amp;#39;s line contents appear in the blame result returned to the caller. Pure VALUE control (the caller forwards a user-influenced revision string). Default `allow_unsafe_options=False`.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
result = repo.blame(&amp;#34;--contents=/etc/passwd&amp;#34;, &amp;#34;a.txt&amp;#34;)
#…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: GitPython&lt;/p&gt;
&lt;p&gt;## Summary
`Repo.blame()` / `Repo.blame_incremental()` guard forwarded revision options against `unsafe_git_revision_options`, but that denylist only contains the file-WRITE options `--output`/`-o`. `git blame` also honors `--contents &amp;lt;file&amp;gt;` and `-S &amp;lt;file&amp;gt;`, which cause the file&amp;#39;s lines to be echoed into the blame result — an arbitrary file READ. Neither option is in the denylist, so a caller-influenced revision value of `--contents=&amp;lt;path&amp;gt;` passes the guard and leaks file contents. This is a distinct sink-option and impact class (READ) from GHSA-956x-8gvw-wg5v (which addressed the blame `--output` WRITE), directly analogous to GHSA-539m-9xh6-q6rr (archive READ gap accepted separately from the archive write/exec advisory).&lt;/p&gt;
&lt;p&gt;## Root Cause
`unsafe_git_revision_options = [&amp;#34;--output&amp;#34;,&amp;#34;-o&amp;#34;]` (`git/repo/base.py:188`). The `rev` string is passed to `_option_candidates([rev], kwargs)` and placed BEFORE the `--` separator (base.py:841). The canonical name of `--contents=...` is `contents`, which is not on the denylist, so no `UnsafeOptionError` is raised. The trailing `--` protects only the pathspec, not the option before the revision.&lt;/p&gt;
&lt;p&gt;## Impact
Arbitrary local file read at the privileges of the host process; the file&amp;#39;s line contents appear in the blame result returned to the caller. Pure VALUE control (the caller forwards a user-influenced revision string). Default `allow_unsafe_options=False`.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
```python
result = repo.blame(&amp;#34;--contents=/etc/passwd&amp;#34;, &amp;#34;a.txt&amp;#34;)
#…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xxx-qhh7-9287</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11615-1 — python313-GitPython-3.1.59-3.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11615-1</link>
      <description>&lt;p&gt;python313-GitPython-3.1.59-3.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python313-GitPython-3.1.59-3.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11615-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3788</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3788</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gitpython&lt;/p&gt;
&lt;p&gt;GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.&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 versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3788</guid>
    </item>
  </channel>
</rss>
