{"answers":{"affected":"2 open source packages ship an affected version, including GitPython and gitpython.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110859 exists.","fix":"Upgrade GitPython to 3.2.0 or later.","what":"CVE-2026-110859 is a high-severity path traversal vulnerability in gitpython-developers GitPython, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-110859 and fix it if it is affected.\n\nWhat it is: CVE-2026-110859 is a high-severity path traversal vulnerability in gitpython-developers GitPython, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110859 exists.\n\nAffected packages and fixed versions:\n- GitPython (PyPI): affected all versions; fixed in 3.2.0\n- gitpython (PyPI): affected all versions; fixed in 3.2.0\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-110859/ (Markdown: https://insights.sbomify.com/CVE-2026-110859/index.md)","id":"CVE-2026-110859","markdown":"https://insights.sbomify.com/CVE-2026-110859/index.md","name":"CVE-2026-110859","record":{"aliases":["DEBIAN-CVE-2026-110859","GHSA-23mf-xhv8-69c2","GHSA-pv89-gqgv-pcc9","MINI-x8v5-mqqj-5q6q","UBUNTU-CVE-2026-110859"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitPython library","requires_auth":"none","summary":"Attackers can read arbitrary files by hosting a repository with a malicious branch name, causing GitPython to leak file contents via error messages.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"GitPython before 3.2.0 contains an argument injection vulnerability in Head.checkout() that allows remote attackers to read arbitrary files by supplying a branch name parsed as a git option. Attackers can host a repository whose default branch is named --pathspec-from-file=\u003cpath\u003e, causing cloning applications that check out the active branch to leak file contents through GitCommandError messages.","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":"GitPython before 3.2.0 Arbitrary File Read via Head.checkout() Branch Name","id":"CVE-2026-110859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"GitPython 3.1.62 before 3.2.0 Symlink Path Traversal via Submodule.move()","id":"CVE-2026-110860"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"GitPython","purl":null,"source":"GHSA-23mf-xhv8-69c2"},{"ecosystem":"PyPI","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-23mf-xhv8-69c2"}],"prev":{"headline":"GitPython 3.1.30 before 3.2.0 Command Injection via Remote.pull() Refspec","id":"CVE-2026-110858"},"products":["GitPython"],"published":"2026-10-14","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["gitpython-developers"]},"summary":"Attackers can read arbitrary files by hosting a repository with a malicious branch name, causing GitPython to leak file contents via error messages.","url":"https://insights.sbomify.com/CVE-2026-110859/"}