{"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-2026-78675 exists.","fix":"Upgrade gitpython to 3.1.59 or later.","what":"CVE-2026-78675 is a high-severity vulnerability in gitpython-developers GitPython, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78675 and fix it if it is affected.\n\nWhat it is: CVE-2026-78675 is a high-severity vulnerability in gitpython-developers GitPython, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78675 exists.\n\nAffected packages and fixed versions:\n- gitpython (PyPI): affected all versions; fixed in 3.1.59\n- gitpython (PyPI): affected all versions; fixed in 3.1.59\n- GitPython (PyPI): affected all versions; fixed in 3.1.59\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-78675/ (Markdown: https://insights.sbomify.com/CVE-2026-78675/index.md)","id":"CVE-2026-78675","markdown":"https://insights.sbomify.com/CVE-2026-78675/index.md","name":"CVE-2026-78675","record":{"aliases":["DEBIAN-CVE-2026-78675","ECHO-c442-4553-3c14","GHSA-7833-fr7j-v32q","MINI-6r37-3r7g-v79x","MINI-7wg4-wmw3-242x","MINI-rv63-j652-rx47","MINI-xh7f-97x8-j58c","PYSEC-2026-3785","ROOT-APP-PYPI-CVE-2026-78675"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python Git library","requires_auth":"none","summary":"Attackers can disclose local file contents by crafting malicious .gitmodules files, exposing sensitive data via exception messages in GitPython.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"gitpython","vendor":"gitpython_project"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file's first line verbatim in the exception message.","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.1.59 Local File Content Disclosure via .gitmodules","id":"CVE-2026-78675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"GitPython before 3.1.59 Remote Code Execution via Config Injection","id":"CVE-2026-78676"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.59"],"introduced":["0"],"last_affected":[],"package":"GitPython","purl":null,"source":"GHSA-7833-fr7j-v32q"},{"ecosystem":"PyPI","fixed":["3.1.59"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-7833-fr7j-v32q"},{"ecosystem":"PyPI","fixed":["3.1.59"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"PYSEC-2026-3785"}],"prev":{"headline":"Remote Code Execution via BPMN System REST APIs in Multiple WSO2 Products Permits Arbitrary Command Execution","id":"CVE-2026-78674"},"products":["GitPython"],"published":"2026-08-25","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":"2026-10-08","vendors":["gitpython-developers"]},"summary":"Attackers can disclose local file contents by crafting malicious .gitmodules files, exposing sensitive data via exception messages in GitPython.","url":"https://insights.sbomify.com/CVE-2026-78675/"}