# CVE-2025-46334: Git GUI malicious command injection on Windows

> A malicious repository can execute arbitrary commands on Windows via Git GUI due to Tcl's unsafe executable search path behavior.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2025-46334, BELL-CVE-2025-46334, GHSA-7px4-9hg2-fvhx

## What is CVE-2025-46334?

CVE-2025-46334 is a high-severity command injection vulnerability in j6t git-gui, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Git GUI allows you to use the Git source control management tools via a GUI. A malicious repository can ship versions of sh.exe or typical textconv filter programs such as astextplain. Due to the unfortunate design of Tcl on Windows, the search path when looking for an executable always includes the current directory. The mentioned programs are invoked when the user selects Git Bash or Browse Files from the menu. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-46334?


## How do I fix CVE-2025-46334?

Upgrade to a fixed version.

## Is CVE-2025-46334 being exploited?

There is no known exploitation of CVE-2025-46334 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46334 and fix it if it is affected.

What it is: CVE-2025-46334 is a high-severity command injection vulnerability in j6t git-gui, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-46334 in the wild and no public exploit code.

Affected product: j6t git-gui. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46334/ (Markdown: https://insights.sbomify.com/CVE-2025-46334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46334
- OSV: https://osv.dev/vulnerability/CVE-2025-46334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46334/
Summaries are generated and may contain mistakes; the official description above is the record.