{"id":"CVE-2023-40590","aliases":["GHSA-wfm5-v35h-vwf4","PYSEC-2023-161"],"title":"GitPython untrusted search path on Windows systems leading to arbitrary code execution","summary":"GitPython untrusted search path on Windows systems leading to arbitrary code execution","severity":"high","cvss":7.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","vendor":"gitpython","product":"gitpython","ecosystem":"pip","affected":["gitpython < 3.1.33"],"patched":["gitpython 3.1.33"],"published":"2023-08-29","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:49:57.778784153Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-wfm5-v35h-vwf4","references":[{"url":"https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-wfm5-v35h-vwf4"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-40590"},{"url":"https://github.com/gitpython-developers/GitPython/issues/1635"},{"url":"https://github.com/gitpython-developers/GitPython/pull/1636"},{"url":"https://github.com/gitpython-developers/GitPython/commit/8b75434e2c8a082cdeb4971cc6f0ee2bafec45bc"},{"url":"https://docs.python.org/3/library/subprocess.html#popen-constructor"},{"url":"https://github.com/gitpython-developers/GitPython"},{"url":"https://github.com/gitpython-developers/GitPython/releases/tag/3.1.33"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/gitpython/PYSEC-2023-161.yaml"}],"tags":["osv","pip"],"epss":0.00504,"epssPercentile":0.40478,"ingestedAt":"2026-09-12T03:13:01.735Z","slug":"CVE-2023-40590","body":"## Overview\n\n### Summary\n\nWhen resolving a program, Python/Windows look for the current working directory, and after that the PATH environment (see big warning in https://docs.python.org/3/library/subprocess.html#popen-constructor). GitPython defaults to use the `git` command, if a user runs GitPython from a repo has a `git.exe` or `git` executable, that program will be run instead of the one in the user's `PATH`.\n\n### Details\n\nThis is more of a problem on how Python interacts with Windows systems, Linux and any other OS aren't affected by this. But probably people using GitPython usually run it from the CWD of a repo.\n\nThe execution of the `git` command happens in\n\nhttps://github.com/gitpython-developers/GitPython/blob/1c8310d7cae144f74a671cbe17e51f63a830adbf/git/cmd.py#L277 \n\nhttps://github.com/gitpython-developers/GitPython/blob/1c8310d7cae144f74a671cbe17e51f63a830adbf/git/cmd.py#L983-L996\n\nAnd there are other commands executed that should probably be aware of this problem.\n\n### PoC\n\nOn a Windows system, create a `git.exe` or `git` executable in any directory, and import or run GitPython from that directory\n\n```\npython -c \"import git\"\n```\n\nThe git executable from the current directory will be run.\n\n### Impact\n\nAn attacker can trick a user to download a repository with a malicious `git` executable, if the user runs/imports GitPython from that directory, it allows the attacker to run any arbitrary commands.\n\n### Possible solutions\n \n- Default to an absolute path for the git program on Windows, like `C:\\\\Program Files\\\\Git\\\\cmd\\\\git.EXE` (default git path installation).\n- Require users to set the `GIT_PYTHON_GIT_EXECUTABLE` environment variable on Windows systems.\n- Make this problem prominent in the documentation and advise users to never run GitPython from an untrusted repo, or set the `GIT_PYTHON_GIT_EXECUTABLE` env var to an absolute path.\n- Resolve the executable manually by only looking into the `PATH` environment variable (suggested by @Byron)\n\n---\n\n> [!NOTE]\n> This vulnerability was reported via email, and it was decided to publish it here and make it public, so the community is aware of it, and a fix can be provided.\n\n## Affected packages\n\n- `gitpython < 3.1.33`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `gitpython 3.1.33`","depth":"twilight","depthScore":43,"depthScoreParts":{"impact":42.9,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}