This entry duplicated another and was withdrawn in its favour.
Superseded by ETK-2026-1615.
ETK-2026-285Zero's internal tracking ID, independent of the CVE number.
withdrawndescription
GitPython versions before 3.2.0 mishandle option-like refspec values passed to Remote.pull(). An attacker may execute commands with the calling process's privileges when an application passes attacker-controlled refspec input and uses a local-path or SSH remote.
mitigation
Upgrade GitPython to >= 3.2.0 or later.
fixed in >= 3.2.0
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
No signals recorded for this entry yet.
this entry in the feed
GET /api/v1/feed/ETK-2026-285
{ "etk_id": "ETK-2026-285", "cve_id": null, "display_id": "ETK-2026-285", "ghsa_id": null, "euvd_id": null, "status": "retired", "anchor_state": "awaiting_cve", "title": "Argument injection in GitPython Remote.pull refspec handling", "summary": "GitPython versions before 3.2.0 mishandle option-like refspec values passed to Remote.pull(). An attacker may execute commands with the calling process's privileges when an application passes attacker-controlled refspec input and uses a local-path or SSH remote.", "mitigation": "Upgrade GitPython to >= 3.2.0 or later.", "vendor": "pip", "product": "GitPython", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 3.1.30" ], "ecosystem": "pip", "fixed_versions": [ ">= 3.2.0" ], "package_name": "GitPython", "purl": "pkg:pypi/GitPython" } ], "cwes": [ 78 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": null, "t0_at": null, "signals": {} }
published 2026-10-01 22:19Z
last change 2026-10-15 00:26Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.