{"id":59490,"date":"2025-07-19T11:59:28","date_gmt":"2025-07-19T11:59:28","guid":{"rendered":""},"modified":"2025-10-21T04:13:31","modified_gmt":"2025-10-21T10:13:31","slug":"cve-2025-46334-critical-vulnerability-in-git-gui-enables-potential-system-compromise","status":"publish","type":"post","link":"https:\/\/www.ameeba.com\/blog\/cve-2025-46334-critical-vulnerability-in-git-gui-enables-potential-system-compromise\/","title":{"rendered":"CVE-2025-46334: Critical Vulnerability in Git GUI Enables Potential System Compromise<\/strong>"},"content":{"rendered":"

Overview<\/strong><\/p>\n

The cybersecurity landscape is continuously evolving, with new vulnerabilities being discovered on a regular basis. One such vulnerability, identified as CVE-2025-46334, poses a significant risk to users of Git GUI, a popular interface for the Git source control management tools. This vulnerability allows<\/a> a malicious repository to deliver harmful versions of sh.exe or typical textconv filter programs, such as astextplain, leading to potential system compromise or data leakage.
\nThis vulnerability essentially stems from the design of Tcl on Windows<\/a>, where the search path for an executable always includes the current directory. This comes into action when the user selects Git Bash or Browse Files<\/a> from the menu, consequently invoking the malicious programs. Given the widespread use of Git GUI<\/a>, this vulnerability could have far-reaching implications if not addressed promptly.<\/p>\n

Vulnerability Summary<\/strong><\/p>\n

CVE ID: CVE-2025-46334
\nSeverity: Critical (8.6 CVSS Score)
\nAttack Vector: Remote
\nPrivileges Required: None
\nUser Interaction: Required
\nImpact: Potential system<\/a> compromise or data leakage<\/p>\n

Affected Products<\/strong><\/p>

\r\n

\r\n \r\n \"Ameeba\r\n <\/a>\r\n Share secrets securely\r\n <\/h2>\r\n\r\n

\r\n Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.\r\n <\/p>\r\n\r\n

\r\n Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.\r\n <\/p>\r\n\r\n