https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 13:56:48 +0000 https://vulnerability.circl.lu/vuln/cve-2026-76217 <p><strong>Affected:</strong> gitpython-developers GitPython</p> <p>GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents returned in GitCommandError.stderr.</p> <p><strong>Affected:</strong> gitpython-developers GitPython</p> <p>GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents returned in GitCommandError.stderr.</p> https://vulnerability.circl.lu/vuln/cve-2026-76217 https://vulnerability.circl.lu/vuln/ghsa-hh9p-6wh2-4mfc <p><strong>Affected:</strong> PyPI: GitPython</p> <p>## Summary</p> <p>`IndexFile.remove()` and `Head.checkout()` forward `**kwargs` into `git rm` and `git checkout` with no guard. Passing `--pathspec-from-file=&lt;file&gt;` **together with `--pathspec-file-nul`** makes Git treat the whole file as a single NUL-delimited pathspec, and the unmatched-pathspec error quotes it verbatim. GitPython surfaces that through `GitCommandError.stderr`, so the entire contents of a caller-chosen file are returned to the caller in band.</p> <p>This is the same primitive as Instance 2 of [GHSA-3f7w-8rr8-f37f](https://github.com/advisories/GHSA-3f7w-8rr8-f37f) - `TagReference.create()` with `-F`, arbitrary file read returned in band - at two sites that advisory assessed and cleared.</p> <p>## Prior art, and why I am filing rather than commenting</p> <p>GHSA-3f7w-8rr8-f37f&#39;s sweep table lists these four sites with the assessment *&#34;`--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found&#34;*:</p> <p>| Call site | git command | that advisory&#39;s assessment | |---|---|---| | `IndexFile.remove()` | `rm` | `--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found | | `IndexFile.move()` | `mv` | same | | `HEAD.reset()` | `reset` | same | | `HEAD.checkout()` | `checkout` | same |</p> <p>That assessment is very nearly right, and I think that is why it held: with `--pathspec-from-file` alone, Git splits on newlines and the error quotes only the **first line**, which reads as an uninteresting partial. Adding `--pathspec-file-nul` - a sibling flag…</p> <p><strong>Affected:</strong> PyPI: GitPython</p> <p>## Summary</p> <p>`IndexFile.remove()` and `Head.checkout()` forward `**kwargs` into `git rm` and `git checkout` with no guard. Passing `--pathspec-from-file=&lt;file&gt;` **together with `--pathspec-file-nul`** makes Git treat the whole file as a single NUL-delimited pathspec, and the unmatched-pathspec error quotes it verbatim. GitPython surfaces that through `GitCommandError.stderr`, so the entire contents of a caller-chosen file are returned to the caller in band.</p> <p>This is the same primitive as Instance 2 of [GHSA-3f7w-8rr8-f37f](https://github.com/advisories/GHSA-3f7w-8rr8-f37f) - `TagReference.create()` with `-F`, arbitrary file read returned in band - at two sites that advisory assessed and cleared.</p> <p>## Prior art, and why I am filing rather than commenting</p> <p>GHSA-3f7w-8rr8-f37f&#39;s sweep table lists these four sites with the assessment *&#34;`--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found&#34;*:</p> <p>| Call site | git command | that advisory&#39;s assessment | |---|---|---| | `IndexFile.remove()` | `rm` | `--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found | | `IndexFile.move()` | `mv` | same | | `HEAD.reset()` | `reset` | same | | `HEAD.checkout()` | `checkout` | same |</p> <p>That assessment is very nearly right, and I think that is why it held: with `--pathspec-from-file` alone, Git splits on newlines and the error quotes only the **first line**, which reads as an uninteresting partial. Adding `--pathspec-file-nul` - a sibling flag…</p> https://vulnerability.circl.lu/vuln/ghsa-hh9p-6wh2-4mfc https://vulnerability.circl.lu/vuln/pysec-2026-3841 <p><strong>Affected:</strong> PyPI: gitpython</p> <p>## Summary</p> <p>`IndexFile.remove()` and `Head.checkout()` forward `**kwargs` into `git rm` and `git checkout` with no guard. Passing `--pathspec-from-file=&lt;file&gt;` **together with `--pathspec-file-nul`** makes Git treat the whole file as a single NUL-delimited pathspec, and the unmatched-pathspec error quotes it verbatim. GitPython surfaces that through `GitCommandError.stderr`, so the entire contents of a caller-chosen file are returned to the caller in band.</p> <p>This is the same primitive as Instance 2 of [GHSA-3f7w-8rr8-f37f](https://github.com/advisories/GHSA-3f7w-8rr8-f37f) - `TagReference.create()` with `-F`, arbitrary file read returned in band - at two sites that advisory assessed and cleared.</p> <p>## Prior art, and why I am filing rather than commenting</p> <p>GHSA-3f7w-8rr8-f37f&#39;s sweep table lists these four sites with the assessment *&#34;`--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found&#34;*:</p> <p>| Call site | git command | that advisory&#39;s assessment | |---|---|---| | `IndexFile.remove()` | `rm` | `--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found | | `IndexFile.move()` | `mv` | same | | `HEAD.reset()` | `reset` | same | | `HEAD.checkout()` | `checkout` | same |</p> <p>That assessment is very nearly right, and I think that is why it held: with `--pathspec-from-file` alone, Git splits on newlines and the error quotes only the **first line**, which reads as an uninteresting partial. Adding `--pathspec-file-nul` - a sibling flag…</p> <p><strong>Affected:</strong> PyPI: gitpython</p> <p>## Summary</p> <p>`IndexFile.remove()` and `Head.checkout()` forward `**kwargs` into `git rm` and `git checkout` with no guard. Passing `--pathspec-from-file=&lt;file&gt;` **together with `--pathspec-file-nul`** makes Git treat the whole file as a single NUL-delimited pathspec, and the unmatched-pathspec error quotes it verbatim. GitPython surfaces that through `GitCommandError.stderr`, so the entire contents of a caller-chosen file are returned to the caller in band.</p> <p>This is the same primitive as Instance 2 of [GHSA-3f7w-8rr8-f37f](https://github.com/advisories/GHSA-3f7w-8rr8-f37f) - `TagReference.create()` with `-F`, arbitrary file read returned in band - at two sites that advisory assessed and cleared.</p> <p>## Prior art, and why I am filing rather than commenting</p> <p>GHSA-3f7w-8rr8-f37f&#39;s sweep table lists these four sites with the assessment *&#34;`--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found&#34;*:</p> <p>| Call site | git command | that advisory&#39;s assessment | |---|---|---| | `IndexFile.remove()` | `rm` | `--pathspec-from-file` only reads a pathspec; no write or disclosure primitive found | | `IndexFile.move()` | `mv` | same | | `HEAD.reset()` | `reset` | same | | `HEAD.checkout()` | `checkout` | same |</p> <p>That assessment is very nearly right, and I think that is why it held: with `--pathspec-from-file` alone, Git splits on newlines and the error quotes only the **first line**, which reads as an uninteresting partial. Adding `--pathspec-file-nul` - a sibling flag…</p> https://vulnerability.circl.lu/vuln/pysec-2026-3841