{"answers":{"affected":"2 open source packages ship an affected version, including Gitpython and gitpython.","exploited":"There is no known exploitation of CVE-2026-114145 in the wild and no public exploit code.","fix":"Upgrade Gitpython to 3.2.1 or later.","what":"CVE-2026-114145 is a high-severity vulnerability in gitpython-developers GitPython, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114145 and fix it if it is affected.\n\nWhat it is: CVE-2026-114145 is a high-severity vulnerability in gitpython-developers GitPython, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-114145 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Gitpython (PyPI): affected all versions; fixed in 3.2.1\n- gitpython (PyPI): affected all versions; fixed in 3.2.1\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-2026-114145/ (Markdown: https://insights.sbomify.com/CVE-2026-114145/index.md)","id":"CVE-2026-114145","markdown":"https://insights.sbomify.com/CVE-2026-114145/index.md","name":"CVE-2026-114145","record":{"aliases":["CLSA-2026-1792741260","DEBIAN-CVE-2026-114145","ECHO-5e70-37df-b83d","GHSA-83vg-56qc-22m7","MINI-qvx6-jjgm-mqm5","UBUNTU-CVE-2026-114145"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-696","name":"Incorrect Behavior Order"}],"description":"GitPython is a python library used to interact with Git repositories. Prior to 3.2.1, create_submodule() in git/objects/submodule/base.py accepts an attacker-influenced submodule path such as .git/hooks and invokes _clone_repo() before safely rejecting the destination. In 3.1.x, _validate_repo_path() does not exist and the call succeeds silently, while in 3.2.0 and later affected revisions the check in git/index/base.py raises ValueError only after the clone has written to disk and does not remove the planted file. An attacker-controlled submodule can therefore place an executable post-checkout hook that a later Git operation executes. Exploitation requires an application to accept an untrusted submodule path and a clone destination such as .git/hooks that is empty enough for Git to clone into it, which commonly means that default sample hooks are absent. This issue is fixed in version 3.2.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"GitPython validates a submodule's \".git\" path only after cloning into it (RCE)","id":"CVE-2026-114145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"ASP.NET Core Elevation of Privilege Vulnerability","id":"CVE-2026-114148"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.1"],"introduced":["0"],"last_affected":[],"package":"Gitpython","purl":null,"source":"GHSA-83vg-56qc-22m7"},{"ecosystem":"PyPI","fixed":["3.2.1"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-83vg-56qc-22m7"}],"prev":{"headline":"toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()","id":"CVE-2026-114144"},"products":["GitPython"],"published":"2026-10-21","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["gitpython-developers"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114145/"}