VYPR
Low severity3.3OSV Advisory· Published May 21, 2025· Updated Apr 15, 2026

CVE-2025-48064

CVE-2025-48064

Description

GitHub Desktop is an open-source, Electron-based GitHub app designed for git development. Prior to version 3.4.20-beta3, an attacker convincing a user to view a file in a commit of their making in the history view can cause information disclosure by means of Git attempting to access a network share. This affects GitHub Desktop users on Windows that view malicious commits in the history view. macOS users are not affected. When viewing a file diff in the history view GitHub Desktop will call git log or git diff with the object id (SHA) of the commit, the name of the file, and the old name of the file if the file has been renamed. As a security precaution Git will attempt to fully resolve the old and new path via realpath, traversing symlinks, to ensure that the resolved paths reside within the repository working directory. This can lead to Git attempting to access a path that resides on a network share (UNC path) and in doing so Windows will attempt to perform NTLM authentication which passes information such as the computer name, the currently signed in (Windows) user name, and an NTLM hash. GitHub Desktop 3.4.20 and later fix this vulnerability. The beta channel includes the fix in 3.4.20-beta3. As a workaround to use until upgrading is possible, only browse commits in the history view that comes from trusted sources.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

GitHub Desktop on Windows prior to 3.4.20 can leak NTLM credentials when viewing a maliciously crafted file rename in the history view.

The vulnerability resides in how GitHub Desktop processes file renames when a user views a file diff in the history view. The application calls git log or git diff with the commit SHA, the current file name, and the old file name if the file was renamed. As a security measure, Git attempts to fully resolve both old and new paths via realpath, traversing symlinks to verify they reside within the repository working directory. This behavior can be exploited: if an attacker crafts a commit with a file rename pointing to a UNC path on a remote network share, Git will attempt to access that path, triggering Windows NTLM authentication [1].

AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

1

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

1

News mentions

0

No linked articles in our index yet.