CVE-2023-25815

published 25 Apr 2023 · updated 2 Nov 2026

Git looks for localized messages in the wrong place

3.3LowCVSS 3.3EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 2.40.1.

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized messages. And since any authenticated user has the permission to create folders in `C:\` (and since `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may remove the permission to create folders in `C:\`.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MicrosoftVisual Studio
fedoraprojectfedora=37, =38
git-for-windows<2.40.1
git_for_windows_projectgit_for_windows<2.40.12.40.1

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Microsoft, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-25815 severity on Zeptric[![CVE-2023-25815](https://zeptric.io/badge/cve/CVE-2023-25815.svg)](https://zeptric.io/cve/CVE-2023-25815)