{"answers":{"affected":"3 open source packages ship an affected version, including gitpython. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69097 exists.","fix":"Upgrade gitpython to 3.1.53 or later.","what":"CVE-2026-69097 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 3 Aug 2026. 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-2026-69097 and fix it if it is affected.\n\nWhat it is: CVE-2026-69097 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 3 Aug 2026. 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-2026-69097 exists.\n\nAffected packages and fixed versions:\n- gitpython (PyPI): affected all versions; fixed in 3.1.53\n- gitpython (PyPI): affected all versions; fixed in 3.1.53\n- gitpython (PyPI): affected all versions; fixed in 3.1.53\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-69097/ (Markdown: https://insights.sbomify.com/CVE-2026-69097/index.md)","id":"CVE-2026-69097","markdown":"https://insights.sbomify.com/CVE-2026-69097/index.md","name":"CVE-2026-69097","record":{"aliases":["DEBIAN-CVE-2026-69097","ECHO-6b19-bb0e-4e42","ECHO-6d73-52e6-3a0a","GHSA-3rp5-jjmw-4wv2","MINI-4fmj-jp92-65xp","MINI-4p3c-736m-4hgq","MINI-8cv6-88w6-3wqh","MINI-cxpf-2xr2-3h26","MINI-h64p-w94q-gvqv","MINI-qx4m-6rvw-cj2r","OESA-2026-3353","OESA-2026-3354","OESA-2026-3439","PYSEC-2026-3981","ROOT-APP-PYPI-GHSA-3rp5-jjmw-4wv2","UBUNTU-CVE-2026-69097"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GitPython library","requires_auth":"none","summary":"Attackers can achieve remote code execution by injecting malicious git config directives via submodule names in GitPython.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"gitpython","vendor":"gitpython_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"GitPython before 3.1.53 fails to properly escape section names in git config files, allowing attackers to inject arbitrary configuration directives through malicious submodule names. Attackers can inject core.sshCommand or other dangerous config keys into the victim's .git/config via create_submodule or clone_from operations, achieving remote code execution when git performs ssh operations.","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.53 Config Injection via Submodule Names","id":"CVE-2026-69097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"kotaemon 0.12.0 Unauthenticated Remote Code Execution via Insecure Deserialization","id":"CVE-2026-69098"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.53"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":null,"source":"GHSA-3rp5-jjmw-4wv2"},{"ecosystem":"PyPI","fixed":["3.1.53"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-3rp5-jjmw-4wv2"},{"ecosystem":"PyPI","fixed":["3.1.53"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"PYSEC-2026-3981"}],"prev":{"headline":"OpenWrt luci-app-dockerman Read ACL Remote Code Execution","id":"CVE-2026-69096"},"products":["GitPython"],"published":"2026-08-03","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-08-14","vendors":["gitpython-developers"]},"summary":"Attackers can achieve remote code execution by injecting malicious git config directives via submodule names in GitPython.","url":"https://insights.sbomify.com/CVE-2026-69097/"}