CVE-2022-24826

Code execution via empty executable path handling

Published Apr 19, 2022 · Updated Apr 23, 2025

Code execution in GitHub Git LFS 2.12.1 through 3.1.2 allows attackers to run arbitrary code via a malicious repository on Windows. When a required executable is absent from PATH, Git LFS passes an empty path to Go os/exec, which searches the working directory and launches a PATHEXT-matched dot file. A victim must run an affected Git LFS command in the crafted repository while the intended git, cygpath, or uname program is missing from PATH, allowing code to run with the victim's privileges.

CVSS severity7.8
High
EPSS probability2.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code execution in GitHub Git LFS 2.12.1 through 3.1.2 allows attackers to run arbitrary code via a malicious repository on Windows. When a required executable is absent from PATH, Git LFS passes an empty path to Go os/exec, which searches the working directory and launches a PATHEXT-matched dot file. A victim must run an affected Git LFS command in the crafted repository while the intended git, cygpath, or uname program is missing from PATH, allowing code to run with the victim's privileges.

The record

CVE
CVE-2022-24826
Published
Apr 19, 2022
Updated
Apr 23, 2025
Vendor
Twitter
Product
Git LFS
Classifications
CWE-426, T1574.007
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 19, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.1.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Twitter · Git LFSversion=3.1.3

Published CVSS scores

9.8GitHub, Inc. CNA via NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.8GitHub Security AdvisoryCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.4NIST NVDAV:L/AC:M/Au:N/C:P/I:P/A:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-426Untrusted Search Path
T1574.007Path Interception by PATH Environment Variable

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo