<?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:07:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12716</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12716</link>
      <description>bdu:2026-12716</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12716</guid>
    </item>
    <item>
      <title>BREW-aider-CVE-2026-78675 — GitPython: Arbitrary local file content disclosure via [include] directive in untrusted .gitmodules (SubmoduleConfigPar…</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-78675</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;# [HIGH] Arbitrary local file content disclosure via `[include]` directive in untrusted `.gitmodules` (`SubmoduleConfigParser` never disables `merge_includes`)&lt;/p&gt;
&lt;p&gt;- **CWE:** CWE-200 (Exposure of Sensitive Information) / CWE-73 (External Control of File Name or Path)
- **Affected component:** `git/objects/submodule/base.py`, `Submodule._config_parser()` (~line 273) constructing `SubmoduleConfigParser(fp_module, read_only=read_only)`; `git/config.py`, `GitConfigParser.__init__` (`merge_includes` default), `GitConfigParser.read()`/`_included_paths()` (include-path resolution, ~lines 630-685), `GitConfigParser._read()` (~line 493-498, `MissingSectionHeaderError`)
- **Affected version:** GitPython at HEAD (`9729ed3b948f2bde09f1f188c5311e172212b67e`, 2026-08-05, VERSION `3.1.58`)&lt;/p&gt;
&lt;p&gt;## Reachability
`GitConfigParser.__init__` defaults `merge_includes=True`: any config file it parses has its `[include]` (and, when a `repo=` is supplied, `[includeIf ...]`) directives followed and merged in. The maintainers already recognized this as dangerous for one specific case and fixed it in commit `41ecc6a4` (&amp;#34;Disable merge_includes in config writers&amp;#34;), which passes `merge_includes=False` when `Repo.config_writer()` builds its parser (`git/repo/base.py`).&lt;/p&gt;
&lt;p&gt;That fix never touched `Submodule._config_parser()`. This method builds the parser used for **every** read of a repo&amp;#39;s submodule configuration — `repo.submodules`, `Submodule.iter_items()`, `Submodule.config()` — via `SubmoduleConfigParser(fp_mod…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;# [HIGH] Arbitrary local file content disclosure via `[include]` directive in untrusted `.gitmodules` (`SubmoduleConfigParser` never disables `merge_includes`)&lt;/p&gt;
&lt;p&gt;- **CWE:** CWE-200 (Exposure of Sensitive Information) / CWE-73 (External Control of File Name or Path)
- **Affected component:** `git/objects/submodule/base.py`, `Submodule._config_parser()` (~line 273) constructing `SubmoduleConfigParser(fp_module, read_only=read_only)`; `git/config.py`, `GitConfigParser.__init__` (`merge_includes` default), `GitConfigParser.read()`/`_included_paths()` (include-path resolution, ~lines 630-685), `GitConfigParser._read()` (~line 493-498, `MissingSectionHeaderError`)
- **Affected version:** GitPython at HEAD (`9729ed3b948f2bde09f1f188c5311e172212b67e`, 2026-08-05, VERSION `3.1.58`)&lt;/p&gt;
&lt;p&gt;## Reachability
`GitConfigParser.__init__` defaults `merge_includes=True`: any config file it parses has its `[include]` (and, when a `repo=` is supplied, `[includeIf ...]`) directives followed and merged in. The maintainers already recognized this as dangerous for one specific case and fixed it in commit `41ecc6a4` (&amp;#34;Disable merge_includes in config writers&amp;#34;), which passes `merge_includes=False` when `Repo.config_writer()` builds its parser (`git/repo/base.py`).&lt;/p&gt;
&lt;p&gt;That fix never touched `Submodule._config_parser()`. This method builds the parser used for **every** read of a repo&amp;#39;s submodule configuration — `repo.submodules`, `Submodule.iter_items()`, `Submodule.config()` — via `SubmoduleConfigParser(fp_mod…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-78675</guid>
    </item>
    <item>
      <title>EUVD-2026-358606</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358606</link>
      <description>EUVD-2026-358606</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358606</guid>
    </item>
    <item>
      <title>fkie_cve-2026-78675</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78675</link>
      <description>&lt;p&gt;GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file&amp;#39;s first line verbatim in the exception message.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file&amp;#39;s first line verbatim in the exception message.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-78675</guid>
    </item>
    <item>
      <title>GHSA-7833-fr7j-v32q — GitPython: Arbitrary local file content disclosure via [include] directive in untrusted .gitmodules (SubmoduleConfigPar…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7833-fr7j-v32q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: GitPython&lt;/p&gt;
&lt;p&gt;# [HIGH] Arbitrary local file content disclosure via `[include]` directive in untrusted `.gitmodules` (`SubmoduleConfigParser` never disables `merge_includes`)&lt;/p&gt;
&lt;p&gt;- **CWE:** CWE-200 (Exposure of Sensitive Information) / CWE-73 (External Control of File Name or Path)
- **Affected component:** `git/objects/submodule/base.py`, `Submodule._config_parser()` (~line 273) constructing `SubmoduleConfigParser(fp_module, read_only=read_only)`; `git/config.py`, `GitConfigParser.__init__` (`merge_includes` default), `GitConfigParser.read()`/`_included_paths()` (include-path resolution, ~lines 630-685), `GitConfigParser._read()` (~line 493-498, `MissingSectionHeaderError`)
- **Affected version:** GitPython at HEAD (`9729ed3b948f2bde09f1f188c5311e172212b67e`, 2026-08-05, VERSION `3.1.58`)&lt;/p&gt;
&lt;p&gt;## Reachability
`GitConfigParser.__init__` defaults `merge_includes=True`: any config file it parses has its `[include]` (and, when a `repo=` is supplied, `[includeIf ...]`) directives followed and merged in. The maintainers already recognized this as dangerous for one specific case and fixed it in commit `41ecc6a4` (&amp;#34;Disable merge_includes in config writers&amp;#34;), which passes `merge_includes=False` when `Repo.config_writer()` builds its parser (`git/repo/base.py`).&lt;/p&gt;
&lt;p&gt;That fix never touched `Submodule._config_parser()`. This method builds the parser used for **every** read of a repo&amp;#39;s submodule configuration — `repo.submodules`, `Submodule.iter_items()`, `Submodule.config()` — via `SubmoduleConfigParser(fp_mod…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: GitPython&lt;/p&gt;
&lt;p&gt;# [HIGH] Arbitrary local file content disclosure via `[include]` directive in untrusted `.gitmodules` (`SubmoduleConfigParser` never disables `merge_includes`)&lt;/p&gt;
&lt;p&gt;- **CWE:** CWE-200 (Exposure of Sensitive Information) / CWE-73 (External Control of File Name or Path)
- **Affected component:** `git/objects/submodule/base.py`, `Submodule._config_parser()` (~line 273) constructing `SubmoduleConfigParser(fp_module, read_only=read_only)`; `git/config.py`, `GitConfigParser.__init__` (`merge_includes` default), `GitConfigParser.read()`/`_included_paths()` (include-path resolution, ~lines 630-685), `GitConfigParser._read()` (~line 493-498, `MissingSectionHeaderError`)
- **Affected version:** GitPython at HEAD (`9729ed3b948f2bde09f1f188c5311e172212b67e`, 2026-08-05, VERSION `3.1.58`)&lt;/p&gt;
&lt;p&gt;## Reachability
`GitConfigParser.__init__` defaults `merge_includes=True`: any config file it parses has its `[include]` (and, when a `repo=` is supplied, `[includeIf ...]`) directives followed and merged in. The maintainers already recognized this as dangerous for one specific case and fixed it in commit `41ecc6a4` (&amp;#34;Disable merge_includes in config writers&amp;#34;), which passes `merge_includes=False` when `Repo.config_writer()` builds its parser (`git/repo/base.py`).&lt;/p&gt;
&lt;p&gt;That fix never touched `Submodule._config_parser()`. This method builds the parser used for **every** read of a repo&amp;#39;s submodule configuration — `repo.submodules`, `Submodule.iter_items()`, `Submodule.config()` — via `SubmoduleConfigParser(fp_mod…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7833-fr7j-v32q</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:21874-1 — Security update for python-GitPython</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21874-1</link>
      <description>&lt;p&gt;Security update for python-GitPython&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-GitPython&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21874-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3785</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3785</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gitpython&lt;/p&gt;
&lt;p&gt;GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file&amp;#39;s first line verbatim in the exception message.&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.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file&amp;#39;s first line verbatim in the exception message.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3785</guid>
    </item>
  </channel>
</rss>
