Snowflake cli: GitPython: Unsafe option check validates multi_options before shlex.split transformation (CVE-2026-42284)
A vulnerability in GitPython used by snowflake-cli allows unsafe Git clone options to bypass validation. The issue arises because the validation checks the original multi_options list before it is transformed by shlex.split, enabling an attacker to embed unsafe options like '--config core.hooksPath=...' inside a string starting with a safe option. This leads to execution of attacker-controlled Git hooks during cloning. The vulnerability affects snowflake-cli versions from 3.4.1 up to but not including 3.18.0 and has a high severity CVSS score of 8.1. A patch is available to address this issue.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-42284) exists in GitPython's _clone() method where multi_options are validated before being transformed by shlex.split. This allows an attacker to craft a string such as '--branch main --config core.hooksPath=/x' that passes the unsafe option check because the check uses startswith on the original list elements. After splitting, the '--config' option is passed to Git, which applies the configuration and executes attacker-controlled hooks during clone operations. This affects Repo.clone_from(), clone(), and Submodule.update() methods. The vulnerability is demonstrated by a proof-of-concept where a malicious hook is executed despite validation. The issue is similar in nature to CVE-2023-40267. The affected product is snowflake-cli using GitPython versions >=3.4.1 and <3.18.0.
Potential Impact
Applications using snowflake-cli versions >=3.4.1 and <3.18.0 that pass user input to multi_options in GitPython clone operations are vulnerable. An attacker can embed unsafe Git options that bypass validation, leading to execution of arbitrary Git hooks. This can result in arbitrary code execution during repository cloning, compromising confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade snowflake-cli to version 3.18.0 or later where this issue is fixed. Until then, avoid passing untrusted input to multi_options in GitPython clone operations. Follow the vendor advisory for official remediation guidance.
Snowflake cli: GitPython: Unsafe option check validates multi_options before shlex.split transformation (CVE-2026-42284)
Description
A vulnerability in GitPython used by snowflake-cli allows unsafe Git clone options to bypass validation. The issue arises because the validation checks the original multi_options list before it is transformed by shlex.split, enabling an attacker to embed unsafe options like '--config core.hooksPath=...' inside a string starting with a safe option. This leads to execution of attacker-controlled Git hooks during cloning. The vulnerability affects snowflake-cli versions from 3.4.1 up to but not including 3.18.0 and has a high severity CVSS score of 8.1. A patch is available to address this issue.
CVSS v3.1
Score 8.1high
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 (CVE-2026-42284) exists in GitPython's _clone() method where multi_options are validated before being transformed by shlex.split. This allows an attacker to craft a string such as '--branch main --config core.hooksPath=/x' that passes the unsafe option check because the check uses startswith on the original list elements. After splitting, the '--config' option is passed to Git, which applies the configuration and executes attacker-controlled hooks during clone operations. This affects Repo.clone_from(), clone(), and Submodule.update() methods. The vulnerability is demonstrated by a proof-of-concept where a malicious hook is executed despite validation. The issue is similar in nature to CVE-2023-40267. The affected product is snowflake-cli using GitPython versions >=3.4.1 and <3.18.0.
Potential Impact
Applications using snowflake-cli versions >=3.4.1 and <3.18.0 that pass user input to multi_options in GitPython clone operations are vulnerable. An attacker can embed unsafe Git options that bypass validation, leading to execution of arbitrary Git hooks. This can result in arbitrary code execution during repository cloning, compromising confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade snowflake-cli to version 3.18.0 or later where this issue is fixed. Until then, avoid passing untrusted input to multi_options in GitPython clone operations. Follow the vendor advisory for official remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BREW-snowflake-cli-CVE-2026-42284
- Osv Schema Version
- 1.7.3
- Ecosystems
- ["Homebrew"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abb41adf7a7c54106cc3a62
Added to database: 09/29/2026, 04:42:21 UTC
Last enriched: 09/29/2026, 05:00:38 UTC
Last updated: 09/29/2026, 18:11:18 UTC
Views: 14
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.