CVE-2025-46835 is a vulnerability classified under CWE-88 (Improper Neutralization of Argument Delimiters in a Command, also known as Argument Injection) affecting the j6t git-gui application. Git-gui is a graphical interface for Git source control management, widely used by developers to interact with Git repositories. The vulnerability arises when a user clones an untrusted repository containing directories with maliciously crafted names. If the user is tricked into editing files within these directories, git-gui improperly handles the argument delimiters, allowing it to execute commands that create or overwrite arbitrary files for which the user has write permissions. This can lead to unauthorized modification or corruption of files, potentially compromising the confidentiality and integrity of the user's data. The vulnerability affects multiple versions of git-gui prior to the patched releases starting from version 2.43.7 and subsequent patch versions up to 2.50.1. The CVSS v3.1 score is 8.5 (high severity), with attack vector local, low attack complexity, no privileges required, user interaction required, and scope changed. The impact includes high confidentiality and integrity loss and low availability impact. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk in environments where users interact with untrusted repositories. The issue is fixed in versions 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.

For European organizations, this vulnerability could lead to unauthorized file overwrites within development environments, potentially allowing attackers to inject malicious code or tamper with source code integrity. This can compromise software supply chains, leading to downstream security risks in production systems. Confidentiality breaches could occur if sensitive files are overwritten or replaced, and integrity violations could undermine trust in codebases. Availability impact is limited but could disrupt development workflows. Organizations relying heavily on git-gui for source control management, especially those handling external or open-source repositories, face elevated risks. The vulnerability could also facilitate lateral movement or privilege escalation if attackers leverage overwritten files to execute malicious payloads. Given the widespread use of Git and git-gui in European software development, the threat could affect critical infrastructure sectors, technology companies, and government agencies involved in software development or deployment.

1. Immediately upgrade all git-gui installations to the fixed versions (2.43.7 or later patched versions) to eliminate the vulnerability. 2. Implement strict policies to avoid cloning or editing files from untrusted or unknown repositories, especially those with suspicious directory names. 3. Employ repository scanning tools to detect and block repositories containing maliciously named directories or files. 4. Restrict write permissions on critical files and directories to minimize the impact of potential overwrites. 5. Educate developers and users about the risks of interacting with untrusted repositories and the importance of verifying repository sources. 6. Use sandboxed or isolated environments for testing untrusted code to prevent contamination of production environments. 7. Monitor file integrity in development environments to detect unauthorized changes promptly. 8. Integrate security checks into CI/CD pipelines to catch anomalies introduced via source control.