Skip to content
Fencer Intel
high 8.6

CVE-2025-46334 json

Git GUI malicious command injection on Windows

published last yr. modified 4mo ago also EUVD-2025-21003

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • git Linux Micro 6.0 2.51.0-1.1

suse advisories SUSE-SU-2025:20721-1

  • git openSUSE Tumbleweed 2.50.1-1.1

opensuse advisories openSUSE-SU-2025:15337-1

  • git Alpine 3.19 2.43.7-r0
  • git Alpine 3.20 2.45.4-r0
  • git Alpine 3.21 2.47.3-r0
  • git Alpine 3.22 2.49.1-r0
  • git Alpine 3.24, Alpine 3.23 2.50.1-r0

alpine advisories ALPINE-CVE-2025-46334

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-46334 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

  • j6t git-gui

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.