Summary
Git LFS permits exfiltration of credentials via crafted HTTP URLs
Workarounds
There are no workarounds known at this time.
References
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-q6r2-x2cc-vrp7
- https://nvd.nist.gov/vuln/detail/CVE-2024-53263
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53263
- https://github.com/git-lfs/git-lfs/releases/tag/v3.6.1
- git-lfs/git-lfs@0345b6f816
For more information
If you have any questions or comments about this advisory:
- For general questions, start a discussion in the Git LFS discussion forum.
- For reports of additional vulnerabilities, please follow the Git LFS security reporting policy.
Impact
When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the git-credential(1) command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1.
Frequently Asked Questions
- What is CVE-2024-53263? CVE-2024-53263 is a high-severity security vulnerability in github.com/git-lfs/git-lfs/v3 (go), affecting versions >= 3.0.0, <= 3.6.0. It is fixed in 3.6.1.
- Which packages are affected by CVE-2024-53263?
github.com/git-lfs/git-lfs/v3(go) (versions >= 3.0.0, <= 3.6.0)github.com/git-lfs/git-lfs(go) (versions >= 0.1.0, <= 3.0.0)
- Is there a fix for CVE-2024-53263? Yes. CVE-2024-53263 is fixed in 3.6.1. Upgrade to this version or later.
- Is CVE-2024-53263 exploitable, and should I be worried? Whether CVE-2024-53263 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-53263 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-53263? Upgrade
github.com/git-lfs/git-lfs/v3to 3.6.1 or later.