GitPython before 3.2.0 Command Execution via ls_remote ext:: URLs
Published Oct 14, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
GitPython before 3.2.0 Command Execution via ls_remote ext:: URLs
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
GitPython before 3.2.0 contains a remote code execution vulnerability that allows attackers to run commands because Git.ls_remote forwards URLs without check_unsafe_protocols validation. Attackers can supply ext:: remote-helper URLs to execute commands when git permits the ext transport, while merge_base and IndexFile.move also accept unguarded option injection.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- VulnCheck Advisory: GitPython before 3.2.0 Command Execution via ls_remote ext:: URLs ↗
Record history
Published Oct 14, 2026 · Last refreshed Nov 3, 2026