Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-53263

git-lfs: Git LFS permits exfiltration of credentials via crafted HTTP URLs

Overview

Published
14 Jan 2025
Modified
17 Jun 2026
High CVE
3 Registry packages
4 OS packages
11 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

8.1 · HIGH

CVSS 3.1 base score, scored by redhat.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Weakness: CWE-74

Affected packages · 3

Packages affected by CVE-2024-53263
EcosystemPackageVulnerableFixed in
Bitnami git-lfs >=0.1.0, <3.6.1 3.6.1
Go github.com/git-lfs/git-lfs >=0.1.0, <=3.0.0 No fix yet
Go github.com/git-lfs/git-lfs/v3 >=3.0.0, <3.6.1 3.6.1

Open a package to see all its vulnerabilities.

Operating systems · 29 fixes

Azure Linux 1 release · 1 package

fixed 1
git-lfs
Azure Linux fixes for CVE-2024-53263
ReleasePackageFixed in
3.0 git-lfs 0:3.6.1-1.azl3

Oracle Linux 2 releases · 1 package

fixed 2
git-lfs
Oracle Linux fixes for CVE-2024-53263
ReleasePackageFixed in
8 git-lfs 3.4.1-4.el8_10
9 git-lfs 3.4.1-4.el9_5

Photon OS 2 releases · 1 package

fixed 2
git-lfs
Photon OS fixes for CVE-2024-53263
ReleasePackageFixed in
4.0 git-lfs 3.2.0-9.ph4
5.0 git-lfs 3.2.0-15.ph5

Red Hat 2 releases · 1 package

fixed 8
git-lfs
Red Hat fixes for CVE-2024-53263
ReleasePackageFixed inAdvisory
8 git-lfs 0:2.13.3-3.el8_4.1 RHSA-2025:0825
8 git-lfs 0:2.13.3-3.el8_6.3 RHSA-2025:0765
8 git-lfs 0:3.2.0-2.el8_8.3 RHSA-2025:0762
8 git-lfs 0:3.4.1-4.el8_10 RHSA-2025:0845
9 git-lfs 0:2.13.3-5.el9_0.3 RHSA-2025:0758
9 git-lfs 0:3.2.0-2.el9_2.2 RHSA-2025:0757

2 more rows

alma 2 releases · 1 package

fixed 2
git-lfs
alma fixes for CVE-2024-53263
ReleasePackageFixed in
8 git-lfs 3.4.1-4.el8_10
9 git-lfs 3.4.1-4.el9_5

amazon linux 1 release · 1 package

fixed 1
git-lfs
amazon linux fixes for CVE-2024-53263
ReleasePackageFixed in
2023 git-lfs +2 3.4.0-78.amzn2023.0.4

debian 4 releases · 1 package

fixed 4
git-lfs
debian fixes for CVE-2024-53263
ReleasePackageFixed in
11 git-lfs 2.13.2-1+deb11u1
12 git-lfs 3.3.0-1+deb12u1
13 git-lfs 3.5.0-2
14 git-lfs 3.5.0-2

echo 1 release · 1 package

fixed 1
git-lfs
echo fixes for CVE-2024-53263
ReleasePackageFixed in
git-lfs 3.5.0-2

openSUSE 1 release · 2 packages

fixed 2
govulncheck-vulndb git-lfs
openSUSE fixes for CVE-2024-53263
ReleasePackageFixed inAdvisory
Tumbleweed govulncheck-vulndb 0.0.20250115T172141-1.1 openSUSE-SU-2025:14653-1
Tumbleweed git-lfs 3.6.1-1.1 openSUSE-SU-2025:14649-1

rocky 2 releases · 1 package

fixed 2
git-lfs
rocky fixes for CVE-2024-53263
ReleasePackageFixed in
8 git-lfs 3.4.1-4.el8_10
9 git-lfs 3.4.1-4.el9_4

ubuntu 4 releases · 1 package

fixed 2 affected 2
git-lfs
ubuntu fixes for CVE-2024-53263
ReleasePackageFixed in
18.04-ESM git-lfs 2.3.4-1ubuntu0.1~esm1
20.04-ESM git-lfs 2.9.2-1ubuntu0.1~esm2
22.04 git-lfs affected
24.04 git-lfs affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.