{"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-44244 exists.","fix":"Upgrade gitpython to 3.1.49 or later.","what":"CVE-2026-44244 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 7 May 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-44244 and fix it if it is affected.\n\nWhat it is: CVE-2026-44244 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 7 May 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-44244 exists.\n\nAffected packages and fixed versions:\n- gitpython (PyPI): affected all versions; fixed in 3.1.49\n- gitpython (PyPI): affected all versions; fixed in 3.1.49\n- GitPython (PyPI): affected all versions; fixed in 3.1.49\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-44244/ (Markdown: https://insights.sbomify.com/CVE-2026-44244/index.md)","id":"CVE-2026-44244","markdown":"https://insights.sbomify.com/CVE-2026-44244/index.md","name":"CVE-2026-44244","record":{"aliases":["CLSA-2026-1784077474","DEBIAN-CVE-2026-44244","ECHO-75d1-905c-5401","GHSA-v87r-6q3f-2j67","MINI-frg6-4pwp-f3xw","MINI-hv35-79fw-5cwj","PYSEC-2026-2163","ROOT-APP-PYPI-CVE-2026-44244","UBUNTU-CVE-2026-44244"],"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":"low_privilege","summary":"Attackers can inject newlines into Git config values to set core.hooksPath, leading to remote code execution when Git hooks are triggered.","user_interaction":"not_required","vuln_class":"code_injection"},"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:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"GitPython is a python library used to interact with Git repositories. Prior to version 3.1.49, GitConfigParser.set_value() passes values to Python's configparser without validating for newlines. GitPython's own _write() converts embedded newlines into indented continuation lines (e.g. \\n becomes \\n\\t), but Git still accepts an indented [core] stanza as a section header — so the injected core.hooksPath becomes effective configuration. Any Git operation that invokes hooks (commit, merge, checkout) will then execute scripts from the attacker-controlled path. This issue has been patched in version 3.1.49.","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: Newline injection in config_writer().set_value() enables RCE via core.hooksPath","id":"CVE-2026-44244","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":"Kyverno: [policy-reporter-ui] XSS via Stored Property Values in PropertyCard Component","id":"CVE-2026-44245"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.49"],"introduced":["0"],"last_affected":[],"package":"GitPython","purl":null,"source":"GHSA-v87r-6q3f-2j67"},{"ecosystem":"PyPI","fixed":["3.1.49"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"GHSA-v87r-6q3f-2j67"},{"ecosystem":"PyPI","fixed":["3.1.49"],"introduced":["0"],"last_affected":[],"package":"gitpython","purl":"pkg:pypi/gitpython","source":"PYSEC-2026-2163"}],"prev":{"headline":"GitPython: Path traversal in GitPython reference APIs allows arbitrary file write and delete outside the repository","id":"CVE-2026-44243"},"products":["GitPython"],"published":"2026-05-07","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-05-09","vendors":["gitpython-developers"]},"summary":"Attackers can inject newlines into Git config values to set core.hooksPath, leading to remote code execution when Git hooks are triggered.","url":"https://insights.sbomify.com/CVE-2026-44244/"}