CVE-2024-53263 — git-lfs
Fix: git-lfs/git-lfs@0345b6fCVE-2024-53263 is a CWE-74 vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.
Git LFS permits exfiltration of credentials via crafted HTTP URLs
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-53263.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Patches
This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/git-lfs/git-lfs | ≥ 0.1.0 | No fix |
| 🐹Go | github.com/git-lfs/git-lfs/v3 | ≥ 3.0.0&&< 3.6.1 | 3.6.1go get github.com/git-lfs/git-lfs/v3@v3.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of github.com/git-lfs/git-lfs has shipped for CVE-2024-53263 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-53263 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-53263. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability in Git LFS is important rather than moderate because it directly impacts the security of credential handling, a core aspect of repository access control. By allowing an attacker to inject line-ending control characters, such as LF or CR, into URLs passed to the `git-credential` command, it bypasses…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | git-lfs-0:3.4.1-4.el8_10 | RHSA-2025:0845 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_4.1 | RHSA-2025:0825 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_6.3 | RHSA-2025:0765 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | git-lfs-0:3.2.0-2.el8_8.3 | RHSA-2025:0762 |
| Red Hat Enterprise Linux 9 | git-lfs-0:3.4.1-4.el9_5 | RHSA-2025:0673 |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | git-lfs-0:2.13.3-5.el9_0.3 | RHSA-2025:0758 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | git-lfs-0:3.2.0-2.el9_2.2 | RHSA-2025:0757 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | git-lfs-0:3.4.1-4.el9_4.1 | RHSA-2025:0759 |
Frequently Asked Questions
Is CVE-2024-53263 in your dependencies?
O3 Security finds CVE-2024-53263 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.