How severe is CVE-2024-53263?

No CVSS score has been assigned to CVE-2024-53263 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-53263?

CVE-2024-53263 affects the following packages: github.com/git-lfs/git-lfs (Go), github.com/git-lfs/git-lfs/v3 (Go). Ecosystems affected: Go.

How do I fix CVE-2024-53263?

A fix is available for CVE-2024-53263; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2024-53263 in my Go dependencies?

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.

How do I mitigate CVE-2024-53263 if there is no patch (or I can't update yet)?

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.

Is CVE-2024-53263 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-53263 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-53263?

CVE-2024-53263 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-53263?

CVE-2024-53263 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-53263 published, and has it been updated?

CVE-2024-53263 was published on January 14, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-53263 — git-lfs

Fix: git-lfs/git-lfs@0345b6f

CVE-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

Also known asBIT-git-lfs-2024-53263GHSA-q6r2-x2cc-vrp7GO-2025-3390

Published

Jan 14, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3

Real-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

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

2 total 1 fixed

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.1`go get github.com/git-lfs/git-lfs/v3@v3.6.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
A fix is available for CVE-2024-53263; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.
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.

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.

Red HatImportant

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…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for CVE-2024-53263 (CC BY 4.0)

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

### 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

O3 Security · Impact-Aware SCA

Is CVE-2024-53263 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works