Read the docs
TI-2024-33773 Aliases CVE-2024-50338GHSA-86c2-4x57-wc8g

Carriage-return character in remote URL allows malicious repository to leak credentials in Git Credential Manager

Priority LOW 38CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-200.

Summary

Git Credential Manager (GCM) is a secure Git credential helper built on .NET that runs on Windows, macOS, and Linux. The Git credential protocol is text-based over standard input/output, and consists of a series of lines of key-value pairs in the format `key=value`. Git's documentation restricts the use of the NUL (`\0`) character and newlines to form part of the keys or values. When Git reads from standard input, it considers both LF and CRLF as newline characters for the credential protocol by virtue of calling `strbuf_getline` that calls to `strbuf_getdelim_strip_crlf`. Git also validates that a newline is not present in the value by checking for the presence of the line-feed character (LF, `\n`), and errors if this is the case. This captures both LF and CRLF-type newlines. Git Credential Manager uses the .NET standard library `StreamReader` class to read the standard input stream line-by-line and parse the `key=value` credential protocol format. The implementation of the `ReadLineAsync` method considers LF, CRLF, and CR as valid line endings. This is means that .NET considers a single CR as a valid newline character, whereas Git does not. This mismatch of newline treatment between Git and GCM means that an attacker can craft a malicious remote URL. When a user clones or otherwise interacts with a malicious repository that requires authentication, the attacker can capture credentials for another Git remote. The attack is also heightened when cloning from repositories with submodules when using the `--recursive` clone option as the user is not able to inspect the submodule remote URLs beforehand. This issue has been patched in version 2.6.1 and all users are advised to upgrade. Users unable to upgrade should only interact with trusted remote repositories, and not clone with `--recursive` to allow inspection of any submodule URLs before cloning those submodules.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.03171 88th percentileScored 2026-11-07
Fix Fixed git-credential-manager (git-ecosystem): 2.6.1git-credential-manager (NuGet): 2.6.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
git-ecosystemgit-credential-managerbefore 2.6.12.6.1Patch availableCNA
—git-credential-manager (NuGet)before 2.6.12.6.1Patch availableGHSA-86c2-4x57-wc8g
  • git-credential-manager Vendorgit-ecosystem Affected before 2.6.1 Fixed in 2.6.1 Patch available CNA
  • git-credential-manager (NuGet) Vendor— Affected before 2.6.1 Fixed in 2.6.1 Patch available GHSA-86c2-4x57-wc8g

Remediation

  • Fix · CNA git-credential-manager (git-ecosystem) Fixed in 2.6.1
  • Fix · GHSA-86c2-4x57-wc8g git-credential-manager (NuGet) Fixed in 2.6.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-50338
  2. 2026-10-03 Alias added: GHSA-86c2-4x57-wc8g

References

  • TI-2024-21372 Git Credential Manager (GCM)'s Debian package does not set root ownership on installed files CVSS 3.1MEDIUM 6.9

Sources