CVE-2026-67322: Exposure of Sensitive Information to an Unauthorized Actor in gitpython-developers GitPython
GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.
AI Analysis
Technical Summary
GitPython before version 3.1.52 is vulnerable to exposure of sensitive environment variables during repository cloning. The vulnerability arises in the Repo.clone_from() function, which uses Git.polish_url() to process the remote URL. On non-Cygwin platforms, Git.polish_url() calls os.path.expandvars() on the URL, expanding any environment variable tokens embedded by an attacker. This results in secrets from the hosting process's environment being included in the URL transmitted over the network to an attacker-controlled server, leading to sensitive information disclosure.
Potential Impact
An attacker who can control the clone URL can cause the hosting process to leak environment variables containing sensitive information such as credentials or tokens. This disclosure occurs without authentication or user interaction and can lead to compromise of secrets used by the application or environment. The vulnerability has a high severity score (CVSS 8.7) due to the network exposure of sensitive data and lack of required privileges or user interaction.
Mitigation Recommendations
A patch is available that fixes this vulnerability in GitPython version 3.1.52 and later. Users should upgrade to version 3.1.52 or newer to remediate the issue. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with the vendor that their environment is updated accordingly. Until patched, avoid cloning from untrusted or attacker-controlled URLs that could embed environment variable tokens.
CVE-2026-67322: Exposure of Sensitive Information to an Unauthorized Actor in gitpython-developers GitPython
Description
GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.
CVSS v4.0
Score 8.7high
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
GitPython before version 3.1.52 is vulnerable to exposure of sensitive environment variables during repository cloning. The vulnerability arises in the Repo.clone_from() function, which uses Git.polish_url() to process the remote URL. On non-Cygwin platforms, Git.polish_url() calls os.path.expandvars() on the URL, expanding any environment variable tokens embedded by an attacker. This results in secrets from the hosting process's environment being included in the URL transmitted over the network to an attacker-controlled server, leading to sensitive information disclosure.
Potential Impact
An attacker who can control the clone URL can cause the hosting process to leak environment variables containing sensitive information such as credentials or tokens. This disclosure occurs without authentication or user interaction and can lead to compromise of secrets used by the application or environment. The vulnerability has a high severity score (CVSS 8.7) due to the network exposure of sensitive data and lack of required privileges or user interaction.
Mitigation Recommendations
A patch is available that fixes this vulnerability in GitPython version 3.1.52 and later. Users should upgrade to version 3.1.52 or newer to remediate the issue. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with the vendor that their environment is updated accordingly. Until patched, avoid cloning from untrusted or attacker-controlled URLs that could embed environment variable tokens.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T13:07:21.183Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a6deb26bf32cb7a34c1fc09
Added to database: 08/01/2026, 12:48:38 UTC
Last enriched: 08/01/2026, 13:04:37 UTC
Last updated: 08/01/2026, 21:20:34 UTC
Views: 6
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.