dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-46334

HIGH · 8.6 CVSS v3.1 Published 2025-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Git GUI on Windows contains a path injection vulnerability where a malicious repository can ship executables (sh.exe or textconv filters like astextplain) that get executed when users select Git Bash or Browse Files from the menu. Due to Tcl's design on Windows, the current directory is always searched for executables before system paths, allowing the malicious code to run with the user's privileges.

MitigationUpdate Git GUI to one of the patched versions (2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, or 2.50.1) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Windows platform
    Check if the operating system is Windows. On Windows, run 'systeminfo | findstr /B /C:"OS Name"' or check environment: 'echo %OS%'. On non-Windows systems, this vulnerability does not apply.
    Affected if The system is not Windows - the vulnerability only affects Git GUI on Windows due to Tcl's executable search behavior.
  2. Locate Git GUI installation
    Check if git-gui.exe exists on the system. Common paths: 'C:\Program Files\Git\git-gui.exe' or 'C:\Program Files (x86)\Git\git-gui.exe'. Use 'where git-gui.exe' or search the filesystem.
    Affected if Git GUI is not installed - no action needed.
  3. Determine installed Git GUI version
    Run 'git gui --version' or right-click git-gui.exe, select Properties, and check the Version tab. Compare the version number against the affected range: versions prior to 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, or 2.50.1.
    Affected if The installed version is earlier than the patched versions listed - the system may be vulnerable.
  4. Identify if user runs Git Bash or Browse Files
    Review user workflows for opening untrusted repositories. Check if users execute 'Git Bash here' context menu or use Browse Files menu option within Git GUI when cloning or working with repositories of unknown origin.
    Affected if Users routinely interact with untrusted repositories using Git Bash or Browse Files features - exploitation requires these actions.

A user is affected if running Git GUI on Windows with a version earlier than the patched releases and who executes Git Bash or Browse Files from within untrusted repositories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Git GUI to one of the patched versions (2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, or 2.50.1) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to Git for Windows 2.50.1 (or latest stable), which contains the fix in git-gui

  1. Determine current Git for Windows version by running `git --version` in command prompt or PowerShell
  2. If the installed version is earlier than 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, or 2.50.1, download and install the latest stable Git for Windows release from https://git-scm.com/download/win
  3. After installation, verify the version by running `git --version` to confirm the upgrade was successful
  4. Ensure you are not using a Git GUI version from an untrusted source; only use official Git for Windows distributions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46334 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data