Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-24826: On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe

60
This week
CRITICAL 9.8REMOTEUPGRADE

CVE-2022-24826 is a critical-severity flaw (CVSS 9.8) affecting git large file storage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and `git.exe` is not found in `PATH`, the `..exe` program will be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. Similarly, if the malicious repository contains files named `..exe` and `cygpath.exe`, and `cygpath.exe` is not found in `PATH`, the `..exe` program will be executed when cert

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.2% (top 17%)
CISA exploited listNo
WeaknessCWE-426
Published2022-04-20
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: git large file storage project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

git large file storage project git large file storage UPGRADE
Affected: >= 2.12.1 and < 3.1.3
Fixed in: 3.1.3
Safe to downgrade to: a release before 2.12.1
1. Check installed version
apt-cache policy git-large-file-storage || rpm -q git-large-file-storage || git-large-file-storage --version
2. UPGRADE to 3.1.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade git-large-file-storage
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade git-large-file-storage
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.12.1 (Debian / Ubuntu)
apt-cache madison git-large-file-storage sudo apt install git-large-file-storage=<VERSION_BEFORE_2.12.1> sudo apt-mark hold git-large-file-storage
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list git-large-file-storage sudo dnf downgrade git-large-file-storage-<VERSION_BEFORE_2.12.1> sudo dnf versionlock add git-large-file-storage
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-24826?

git large file storage: upgrade to 3.1.3. Exact commands for each OS are on this page.

Is CVE-2022-24826 being exploited?

CVE-2022-24826 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-24826 affect?

CVE-2022-24826 affects git large file storage. Severity is critical (CVSS 9.8). On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and `git.exe` is not found in `PATH`, the `..exe` program will be executed, permitting the attacker to execute arbitrary code.

How urgent is CVE-2022-24826?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Windows vulnerabilities · Git vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.