Snowflake cli: GitPython: Incomplete unsafe_git_clone_options denylist omits --template enabling arbitrary command execution via clone hooks (CVE-2026-73623)
GitPython's unsafe_git_clone_options denylist omits the --template option, which allows an attacker to specify a directory containing Git hooks that execute during repository cloning. This can lead to arbitrary OS command execution if an attacker can place executable hooks in a directory accessible to the victim. The vulnerability affects snowflake-cli versions from 3.4.1 up to but not including 3.24.0. A patch is available to add --template to the denylist and prevent this attack vector.
AI Analysis
Technical Summary
The vulnerability arises because GitPython's denylist of unsafe git clone options does not include the --template option. The --template option causes git clone to copy hooks from the specified directory into the new repository and execute the post-checkout hook during cloning. An attacker who can influence clone options and stage an executable post-checkout hook in a directory can achieve arbitrary command execution during cloning. This was verified on snowflake-cli up to version 3.1.53 and affects versions >=3.4.1 <3.24.0. The recommended fix is to add --template to the unsafe_git_clone_options denylist.
Potential Impact
An attacker with the ability to influence clone options and stage executable hooks in an attacker-readable directory can execute arbitrary OS commands during the cloning process. This requires a realistic precondition of attacker-writable or shared filesystem access to place malicious hooks. The impact includes full confidentiality, integrity, and availability compromise (CVSS 7.5, high severity).
Mitigation Recommendations
A patch is available that adds --template to the unsafe_git_clone_options denylist, preventing its use in clone_from calls and blocking this attack vector. Users should update snowflake-cli to a fixed version at or above 3.24.0. No additional mitigations are required if the patch is applied.
Snowflake cli: GitPython: Incomplete unsafe_git_clone_options denylist omits --template enabling arbitrary command execution via clone hooks (CVE-2026-73623)
Description
GitPython's unsafe_git_clone_options denylist omits the --template option, which allows an attacker to specify a directory containing Git hooks that execute during repository cloning. This can lead to arbitrary OS command execution if an attacker can place executable hooks in a directory accessible to the victim. The vulnerability affects snowflake-cli versions from 3.4.1 up to but not including 3.24.0. A patch is available to add --template to the denylist and prevent this attack vector.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because GitPython's denylist of unsafe git clone options does not include the --template option. The --template option causes git clone to copy hooks from the specified directory into the new repository and execute the post-checkout hook during cloning. An attacker who can influence clone options and stage an executable post-checkout hook in a directory can achieve arbitrary command execution during cloning. This was verified on snowflake-cli up to version 3.1.53 and affects versions >=3.4.1 <3.24.0. The recommended fix is to add --template to the unsafe_git_clone_options denylist.
Potential Impact
An attacker with the ability to influence clone options and stage executable hooks in an attacker-readable directory can execute arbitrary OS commands during the cloning process. This requires a realistic precondition of attacker-writable or shared filesystem access to place malicious hooks. The impact includes full confidentiality, integrity, and availability compromise (CVSS 7.5, high severity).
Mitigation Recommendations
A patch is available that adds --template to the unsafe_git_clone_options denylist, preventing its use in clone_from calls and blocking this attack vector. Users should update snowflake-cli to a fixed version at or above 3.24.0. No additional mitigations are required if the patch is applied.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BREW-snowflake-cli-CVE-2026-73623
- Osv Schema Version
- 1.7.3
- Ecosystems
- ["Homebrew"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abb41aef7a7c54106cc3a71
Added to database: 09/29/2026, 04:42:22 UTC
Last enriched: 09/29/2026, 05:01:56 UTC
Last updated: 09/29/2026, 05:01:56 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.