{"answers":{"affected":"3 open source packages ship an affected version, including gitpython and GitPython. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40590 exists.","fix":"Upgrade gitpython to 3.1.33 or later.","what":"CVE-2023-40590 is a high-severity path traversal vulnerability in gitpython-developers GitPython, published on 28 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-40590 and fix it if it is affected.\n\nWhat it is: CVE-2023-40590 is a high-severity path traversal vulnerability in gitpython-developers GitPython, published on 28 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40590 exists.\n\nAffected packages and fixed versions:\n- gitpython (PyPI): affected all versions; fixed in 3.1.33\n- gitpython (PyPI): affected all versions; fixed in 3.1.33\n- GitPython (PyPI): affected all versions; fixed in 3.1.33\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-40590/ (Markdown: https://insights.sbomify.com/CVE-2023-40590/index.md)","id":"CVE-2023-40590","markdown":"https://insights.sbomify.com/CVE-2023-40590/index.md","name":"CVE-2023-40590","record":{"aliases":["GHSA-wfm5-v35h-vwf4","PYSEC-2023-161","UBUNTU-CVE-2023-40590"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python Git library","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious git executable in a repository directory, tricking users into running GitPython from that location.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gitpython","vendor":"gitpython_project"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"GitPython is a python library used to interact with Git repositories. When resolving a program, Python/Windows look for the current working directory, and after that the PATH environment. 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`. This 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. An 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. There is no fix currently available for windows users, however there are a few mitigations. 1: Default to an absolute path for the git program on Windows, like `C:\\\\Program Files\\\\Git\\\\cmd\\\\git.EXE` (default git path installation). 2: Require users to set the `GIT_PYTHON_GIT_EXECUTABLE` environment variable on Windows systems. 3: 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. 4: Resolve the executable manually by only looking into the `PATH` environment variable.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Untrusted search path on Windows systems leading to arbitrary code execution","id":"CVE-2023-40590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":3,"n_references":2,"next":{"headline":"Denial of service via malicious p2p message in go-ethereum","id":"CVE-2023-40591"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.33"],"introduced":["0"],"last_affected":[],"package":"GitPython","purl":null,"source":"GHSA-wfm5-v35h-vwf4"},{"ecosystem":"PyPI","fixed":["3.1.33"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-wfm5-v35h-vwf4"},{"ecosystem":"PyPI","fixed":["3.1.33"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"PYSEC-2023-161"}],"prev":{"headline":"FreeRDP Global-Buffer-Overflow in ncrush_decompress","id":"CVE-2023-40589"},"products":["GitPython"],"published":"2023-08-28","related":[{"cvss_score":9.8,"headline":"GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments","id":"CVE-2023-40267","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":9.3,"headline":"GitPython before 3.1.59 Remote Code Execution via Config Injection","id":"CVE-2026-78676","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.3,"headline":"GitPython 3.1.50 Authentication Bypass via Joined Short Options","id":"CVE-2026-67324","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":8.8,"headline":"GitPython: Command injection via Git options bypass","id":"CVE-2026-42215","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.7,"headline":"GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation","id":"CVE-2026-87817","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":8.7,"headline":"GitPython before 3.1.60 Denial of Service via ReDoS","id":"CVE-2026-87819","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":8.7,"headline":"GitPython before 3.1.59 Path Traversal via separate-git-dir","id":"CVE-2026-78677","kev_date_added":null,"published":"2026-08-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-02","vendors":["gitpython-developers"]},"summary":"Attackers can execute arbitrary code by placing a malicious git executable in a repository directory, tricking users into running GitPython from that location.","url":"https://insights.sbomify.com/CVE-2023-40590/"}