Skip to main content
No exploitation reported

CVE-2022-24975

No exploitation reported by the sources we read.

  • Published2022-02-11
  • WeaknessCWE-668

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.

Timeline

dates in UTC
  1. 2022-02-1120:15CVE publishedNVD

Versions per branch

NVD
Git-scm git
BranchAffectedFixed in
2.35≤ 2.35.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gitUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • gitUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • gitUbuntu:Pro:16.04:LTSall versions · no fixed version listed
  • gitUbuntu:22.04:LTSall versions · no fixed version listed
  • gitRoot:Debian:12all versions · fixed in 1:2.39.5-0+deb12u3.root.io.9and 1 other package
  • gitRoot:Debian:12all versions · fixed in 1:2.39.5-0+deb12u3.aikido.10and 1 other package
  • gitDebian:14all versions · no fixed version listed
  • gitDebian:13all versions · no fixed version listed

1 more package range on OSV.dev

Vendor advisories

  • CVE-2022-24975 Red Hat Product Security

    git: The --mirror option for git leaks secret for deleted content, aka the "GitBleed"

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2022-02-11
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-wx8f-p63x-543f

Frequently asked questions

What is CVE-2022-24975?

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.

Is CVE-2022-24975 actively exploited?

Active exploitation of CVE-2022-24975 has not been confirmed. Its EPSS score was 2.6% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-24975?

CVE-2022-24975 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running git? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record