# CVE-2024-53263: Git LFS permits exfiltration of credentials via crafted HTTP URLs > Attackers can exfiltrate Git credentials by injecting control characters into HTTP URLs, affecting all Git LFS users. - **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jan 2025 - **Updated:** 26 Feb 2026 - **Also known as:** ALSA-2025:0673, ALSA-2025:0845, AZL-55644, AZL-55670, BIT-git-lfs-2024-53263, CLSA-2025-1762867600, DEBIAN-CVE-2024-53263, DLA-4028-1, DSA-5849-1, GHSA-q6r2-x2cc-vrp7, GO-2025-3390, MGASA-2025-0028, RHSA-2025:0673, RHSA-2025:0757, RHSA-2025:0758, RHSA-2025:0759, RHSA-2025:0762, RHSA-2025:0765, RHSA-2025:0825, RHSA-2025:0845, RLSA-2025:0673, RLSA-2025:0845, UBUNTU-CVE-2024-53263, openSUSE-SU-2025:0153-1, openSUSE-SU-2025:14649-1 ## What is CVE-2024-53263? CVE-2024-53263 is a high-severity vulnerability in git-lfs, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Git LFS is a Git extension for versioning large files. 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. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2024-53263? 7 open source packages ship an affected version, including github.com/git-lfs/git-lfs, git-lfs and github.com/git-lfs/git-lfs/v3. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/git-lfs/git-lfs` | Go | From 0.1.0 | None | | `github.com/git-lfs/git-lfs` | Go | From 0.1.0 to 3.0.0 | None | | `github.com/git-lfs/git-lfs` | Go | From 0.1.0 to 3.0.0 | None | | `git-lfs` | Bitnami | From 0.1.0 | 3.6.1 | | `github.com/git-lfs/git-lfs/v3` | Go | From 3.0.0 | 3.6.1 | | `github.com/git-lfs/git-lfs/v3` | Go | From 3.0.0 | 3.6.1 | | `github.com/git-lfs/git-lfs/v3` | Go | From 3.0.0 | 3.6.1 | | `git-lfs` | AlmaLinux:8 | All versions | 3.4.1-4.el8_10 | | `git-lfs` | AlmaLinux:9 | All versions | 3.4.1-4.el9_5 | | `git-lfs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.4.1-4.el8_10 | | `git-lfs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.4.1-4.el8_10 | | `git-lfs-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.4.1-4.el8_10 | | `git-lfs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.4.1-4.el9_5 | | `git-lfs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.4.1-4.el9_5 | | `git-lfs-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.4.1-4.el9_5 | | `git-lfs` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | | `git-lfs` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.13.3-3.el8_6.3 | | `git-lfs` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.13.3-5.el9_0.3 | | `git-lfs-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.13.3-5.el9_0.3 | | `git-lfs-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.13.3-5.el9_0.3 | | `git-lfs` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.2.0-2.el8_8.3 | | `git-lfs-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.2.0-2.el8_8.3 | | `git-lfs-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.2.0-2.el8_8.3 | | `git-lfs` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.2.0-2.el9_2.2 | | `git-lfs-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.2.0-2.el9_2.2 | | `git-lfs-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.2.0-2.el9_2.2 | | `git-lfs` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.4.1-4.el9_4.1 | | `git-lfs-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.4.1-4.el9_4.1 | | `git-lfs-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.4.1-4.el9_4.1 | | `git-lfs` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:2.13.3-3.el8_4.1 | ## How do I fix CVE-2024-53263? Upgrade to a fixed version. ## Is CVE-2024-53263 being exploited? There is no known exploitation of CVE-2024-53263 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-53263 and fix it if it is affected. What it is: CVE-2024-53263 is a high-severity vulnerability in git-lfs, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-53263 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/git-lfs/git-lfs (Go): affected from 0.1.0; no fix listed - github.com/git-lfs/git-lfs (Go): affected from 0.1.0 up to 3.0.0; no fix listed - github.com/git-lfs/git-lfs (Go): affected from 0.1.0 up to 3.0.0; no fix listed - git-lfs (Bitnami): affected from 0.1.0; fixed in 3.6.1 - github.com/git-lfs/git-lfs/v3 (Go): affected from 3.0.0; fixed in 3.6.1 - github.com/git-lfs/git-lfs/v3 (Go): affected from 3.0.0; fixed in 3.6.1 - github.com/git-lfs/git-lfs/v3 (Go): affected from 3.0.0; fixed in 3.6.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-53263/ (Markdown: https://insights.sbomify.com/CVE-2024-53263/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53263 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53263 - OSV: https://osv.dev/vulnerability/CVE-2024-53263 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-53263/ Summaries are generated and may contain mistakes; the official description above is the record.