CVSS 4.0
8.5 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NKnown as Clone2Leak
High (8.5) in git-lfs git-lfs. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/git-lfs/git-lfs/v3 3.6.1.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:Ngithub.com/git-lfs/git-lfs/v3 (Go): fixed in 3.6.1Explain CVE-2024-53263 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-53263?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-53263?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-53263 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| git-lfs | >= 0.1.0, < 3.6.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-q6r2-x2cc-vrp7 | Go | github.com/git-lfs/git-lfs | >=0.1.0 <=3.0.0 | no fix published |
| GHSA-q6r2-x2cc-vrp7 | Go | github.com/git-lfs/git-lfs/v3 | >=3.0.0 <3.6.1 | 3.6.1 |
| GO-2025-3390 | Go | github.com/git-lfs/git-lfs | >=0.1.0 | no fix published |
| GO-2025-3390 | Go | github.com/git-lfs/git-lfs/v3 | >=3.0.0 <3.6.1 | 3.6.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 11 | git-lfs | 2.13.2-1+deb11u1 | DLA-4028-1 |
| Debian | 12 | git-lfs | 3.3.0-1+deb12u1 | DEBIAN-CVE-2024-53263 DSA-5849-1 |
| Debian | 13, 14 | git-lfs | 3.5.0-2 | DEBIAN-CVE-2024-53263 |
| Ubuntu | 25.10 | git-lfs | 3.6.1-1ubuntu0.1 | USN-7977-1 |
| Ubuntu | Pro:18.04:LTS | git-lfs | 2.3.4-1ubuntu0.1~esm1 | UBUNTU-CVE-2024-53263 USN-7977-1 |
| Ubuntu | Pro:20.04:LTS | git-lfs | 2.9.2-1ubuntu0.1~esm2 | UBUNTU-CVE-2024-53263 USN-7977-1 |
| Ubuntu | Pro:22.04:LTS | git-lfs | 3.0.2-1ubuntu0.3+esm2 | UBUNTU-CVE-2024-53263 USN-7977-1 |
| Ubuntu | Pro:24.04:LTS | git-lfs | 3.4.1-1ubuntu0.3+esm2 | UBUNTU-CVE-2024-53263 USN-7977-1 |
| Red Hat | enterprise_linux:8::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:3.4.1-4.el8_10 | RHSA-2025:0845 |
| Red Hat | enterprise_linux:9::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:3.4.1-4.el9_5 | RHSA-2025:0673 |
| Red Hat | rhel_aus:8.4::appstream, rhel_e4s:8.4::appstream, rhel_tus:8.4::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:2.13.3-3.el8_4.1 | RHSA-2025:0825 |
| Red Hat | rhel_aus:8.6::appstream, rhel_e4s:8.6::appstream, rhel_tus:8.6::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:2.13.3-3.el8_6.3 | RHSA-2025:0765 |
| Red Hat | rhel_e4s:9.0::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:2.13.3-5.el9_0.3 | RHSA-2025:0758 |
| Red Hat | rhel_eus:8.8::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:3.2.0-2.el8_8.3 | RHSA-2025:0762 |
| Red Hat | rhel_eus:9.2::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:3.2.0-2.el9_2.2 | RHSA-2025:0757 |
| Red Hat | rhel_eus:9.4::appstream | git-lfs, git-lfs-debuginfo, git-lfs-debugsource | 0:3.4.1-4.el9_4.1 | RHSA-2025:0759 |
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 | SUSE-SU-2025:0297-1 |
| SUSE | Package Hub 15 SP6 | git-lfs | 3.6.1-bp156.2.3.1 | openSUSE-SU-2025:0153-1 |
| openSUSE | Leap 15.6 | git-lfs | 3.6.1-bp156.2.3.1 | openSUSE-SU-2025:0153-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 | SUSE-SU-2025:0297-1 |
| openSUSE | Tumbleweed | git-lfs | 3.6.1-1.1 | openSUSE-SU-2025:14649-1 |
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20250115T172141-1.1 | openSUSE-SU-2025:14653-1 |
| AlmaLinux | 8 | git-lfs | 3.4.1-4.el8_10 | ALSA-2025:0845 |
| AlmaLinux | 9 | git-lfs | 3.4.1-4.el9_5 | ALSA-2025:0673 |
| Rocky Linux | 8 | git-lfs | 0:3.4.1-4.el8_10 | RLSA-2025:0845 |
| Rocky Linux | 9 | git-lfs | 0:3.4.1-4.el9_4 | RLSA-2025:0673 |
| Azure Linux | 2 | git-lfs | 3.5.1-4 | AZL-55644 |
| Azure Linux | 3 | git-lfs | 3.6.1-1 | AZL-55670 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.
Red Hat rates this Important.
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 a fundamental trust boundary between Git and the credential helper. This issue could enable attackers to intercept or exfiltrate user credentials, granting unauthorized access to repositories, including private and sensitive data.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | git-lfs-0:3.4.1-4.el8_10 | Fixed 2025-01-30 | RHSA-2025:0845 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_4.1 | Fixed 2025-01-30 | RHSA-2025:0825 |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | git-lfs-0:2.13.3-3.el8_4.1 | Fixed 2025-01-30 | RHSA-2025:0825 |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | git-lfs-0:2.13.3-3.el8_4.1 | Fixed 2025-01-30 | RHSA-2025:0825 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_6.3 | Fixed 2025-01-28 | RHSA-2025:0765 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | git-lfs-0:2.13.3-3.el8_6.3 | Fixed 2025-01-28 | RHSA-2025:0765 |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | git-lfs-0:2.13.3-3.el8_6.3 | Fixed 2025-01-28 | RHSA-2025:0765 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | git-lfs-0:3.2.0-2.el8_8.3 | Fixed 2025-01-28 | RHSA-2025:0762 |
| Red Hat Enterprise Linux 9 | git-lfs-0:3.4.1-4.el9_5 | Fixed 2025-01-23 | RHSA-2025:0673 |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | git-lfs-0:2.13.3-5.el9_0.3 | Fixed 2025-01-28 | RHSA-2025:0758 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | git-lfs-0:3.2.0-2.el9_2.2 | Fixed 2025-01-28 | RHSA-2025:0757 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | git-lfs-0:3.4.1-4.el9_4.1 | Fixed 2025-01-28 | RHSA-2025:0759 |
| Red Hat Enterprise Linux 10 | git-lfs | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-53263.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37).