Public proof of conceptFix available

CVE-2022-39253

Q: Is CVE-2022-39253 actively exploited?

Active exploitation of CVE-2022-39253 has not been confirmed. Its EPSS score was 1.5% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2022-39253?

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

A public proof of concept exists; no exploitation attested.

Published2022-10-19
Fixed in2.37.4 · 2.36.3 · 2.35.5 · 2.34.5 · 2.33.5 · 2.32.4
WeaknessCWE-200 · CWE-59

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

Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.

Timeline

dates in UTC

2022-10-1911:15CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-39253?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-39253?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Git-scm git

Branch	Affected	Fixed in	Source
2.37	≥ 2.37.0, < 2.37.4	2.37.4	NVD
2.36	≥ 2.36.0, < 2.36.3	2.36.3	NVD
2.35	≥ 2.35.0, < 2.35.5	2.35.5	NVD
2.34	≥ 2.34.0, < 2.34.5	2.34.5	NVD
2.33	≥ 2.33.0, < 2.33.5	2.33.5	NVD
2.32	≥ 2.32.0, < 2.32.4	2.32.4	NVD
2.31	≥ 2.31.0, < 2.31.5	2.31.5	NVD
2.30	< 2.30.6	2.30.6	NVD
2.38	= 2.38.0	no fix published	NVD

Fedoraproject fedora

Branch	Affected	Fixed in	Source
35.x	= 35	no fix published	NVD
36.x	= 36	no fix published	NVD
37.x	= 37	no fix published	NVD

Apple xcode

Branch	Affected	Fixed in	Source
14.1	< 14.1	14.1	NVD

1 more product in the sources.

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

gitAlmaLinux:9all versions · fixed in 2.39.1-1.el9and 14 other packages
gitAlmaLinux:8all versions · fixed in 2.39.1-1.el8and 14 other packages

Full record on NVD

Fix

Update Git-scm git to 2.37.4 · 2.36.3 · 2.35.5 · 2.34.5 · 2.33.5 · 2.32.4 · 2.31.5 · 2.30.6

Advisories and patches

github.comMitigation

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 2 repositories, unverifiedssst0n3/docker-cve-2022-39253-pocHiImDarwin/NetworkSecurityFinalProject

Sources

CNACVSS 3.15.5read 2026-10-23
NVDCVSS 3.15.5read 2026-10-23
CNAweakness (CWE)CWE-200read 2026-10-23
NVDweakness (CWE)CWE-59read 2026-10-23
FIRST EPSSEPSS score1.5 %2026-10-23
PoC-in-GitHubproof of concept2read 2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Published: 2022-10-19
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2022-39253?

Is CVE-2022-39253 actively exploited?

Active exploitation of CVE-2022-39253 has not been confirmed. Its EPSS score was 1.5% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

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

CVE-2022-39253 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 product CISA KEV additions, October 2026 Search CVEs

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

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

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

Back to CVE Database