NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
HIGH severity

GHSA-8prw-h3cq-mghm — git

HIGHFix: git/git@684dd4c

GHSA-8prw-h3cq-mghm is a high-severity (CVSS 7.5) CWE-59 vulnerability. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available — see the affected versions and patch details below.

Published
Updated
Affected
4 products
Patched
See advisory
Exploits
3 known
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
88.6%probability of exploitation in next 30 days
Very High Risk+0.11%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
49.8%65.7%81.7%97.6%58.7%88.6%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Description

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

Affected Products

4 products · 20 configurations
Application
xcodeapple
< 12.5
range
OS
debian linuxdebian
1 version
10.0
OS
fedorafedoraproject
3 versions
323334
Application
gitgit-scm
≥ 2.30.0 && ≤ 2.14.2
2 versions
2.27.02.28.0
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Fix

    Upgrade the affected component to the fixed release for GHSA-8prw-h3cq-mghm, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

  3. 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 HatModerate

This vulnerability affects case-insensitive file systems, therefore typical Linux scenarios should be safe. However, as per upstream, exploitation is even possible on Linux under certain circumstances. Red Hat CodeReady Studio 12 is not affected by this flaw because Jboss Forge Addon uses jgit which is a different…

Workaround published by Red Hat
If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources.
Source: Red Hat security advisory for GHSA-8prw-h3cq-mghm (CC BY 4.0)

Frequently Asked Questions

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March
O3 Security · Impact-Aware SCA

Is GHSA-8prw-h3cq-mghm in your dependencies?

Find it across your dependency tree, including transitive dependencies.

GHSA-8prw-h3cq-mghm: git (High 7.5)