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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2024-50338: 3.17% estimated exploitation activity in the next 30 days; percentile 88.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description 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[^1] or values. When Git reads from standard input, it considers both LF and CRLF[^2] as newline characters for the credential protocol by virtue of calling strbufgetline that calls to strbufgetdelimstripcrlf. 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…

Published by the source

14 Jan 2025, 19:40 UTC

Last modified by the source

14 Jan 2025, 21:59 UTC

Source last checked

26 Oct 2026, 17:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-86c2-4x57-wc8g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-50338

Advisory: Git Credential Manager carriage-return character in remote URL allows malicious repository to leak credentials
IDs: CVE-2024-50338, GHSA-86c2-4x57-wc8g
Record: https://patchnext.com/advisories/cve-2024-50338 (revision 1, source checked 26 Oct 2026, 17:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: git-credential-manager 2.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet git-credential-manager: affected <= 2.6.0; fixed in 2.6.1

## Suggested inspection (read-only)
- NuGet git-credential-manager: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on git-credential-manager.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-86c2-4x57-wc8g (GitHub-reviewed advisory GHSA-86c2-4x57-wc8g lists affected ranges: NuGet git-credential-manager >=0 <=2.6.0)

Commands are suggestions: review each one before running it.