Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-39253: Git subject to exposure of sensitive information via local clone of symbolic links

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.7% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: git (AlmaLinux:8) 2.39.1-1.el8; git-all (AlmaLinux:8) 2.39.1-1.el8; git-core (AlmaLinux:8) 2.39.1-1.el8.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to git (AlmaLinux:8) 2.39.1-1.el8; git-all (AlmaLinux:8) 2.39.1-1.el8; git-core (AlmaLinux:8) 2.39.1-1.el8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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`.

MediumCVSS 5.5 · v3.1—Proof of concept Fix available
Published
Oct 19, 2022
Updated
Jun 17, 2026
EPSS
1.4% · 73th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

CNA vs NVD score

NVD
5.5
CNA · GitHub_M
5.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-39253

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
git-scmgit
fedoraprojectfedora
applexcode
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple xcodebefore 14.1
  • debian debian linux10.0
  • fedoraproject fedora35
  • fedoraproject fedora36
  • fedoraproject fedora37
  • git-scm git2.35.0 and later · before 2.35.5
  • git-scm git2.36.0 and later · before 2.36.3
  • git-scm gitbefore 2.30.6
  • git-scm git2.37.0 and later · before 2.37.4
  • git-scm git2.31.0 and later · before 2.31.5
  • git-scm git2.32.0 and later · before 2.32.4
  • git-scm git2.33.0 and later · before 2.33.5
  • git-scm git2.34.0 and later · before 2.34.5
  • git-scm git2.38.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git git

    • < 2.30.6, < 2.31.5, < 2.32.4, < 2.33.5, < 2.34.5, < 2.35.5, < 2.36.3, < 2.37.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8gitbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-allbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-corebefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-core-docbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-credential-libsecretbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-daemonbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-emailbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-guibefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-instawebbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-subtreebefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8git-svnbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8gitkbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8gitwebbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8perl-Gitbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:8perl-Git-SVNbefore 2.39.1-1.el82.39.1-1.el8
AlmaLinux:9gitbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-allbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-corebefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-core-docbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-credential-libsecretbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-daemonbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-emailbefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-guibefore 2.39.1-1.el92.39.1-1.el9
AlmaLinux:9git-instawebbefore 2.39.1-1.el92.39.1-1.el9

+83

Other highest-scoring records for the same primary product.

  • CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2022-24765Apr 12, 2022 · Uncontrolled search for the Git directory in Git for Windows
    31Monitor
  • ← EarlierCVE-2022-29187Jul 12, 2022 · Bypass of safe.directory protections in Git
    31Monitor
  • Later →CVE-2022-39260Oct 19, 2022 · Git vulnerable to Remote Code Execution via Heap overflow in `git shell`
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:git2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.39.1-1.el9 · AlmaLinux:9Package registry (OSV)
alpine:git2.30.6-r0 · Alpine:v3.13Package registry (OSV)
debian:git1:2.38.1-1 · Debian:12Package registry (OSV)
opensuse:docker-compose2.12.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:git2.35.3-150300.10.18.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:perl-Git-Repository1.326.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:reuse1.1.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:git0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-all0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret-debuginfo0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-email0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:102022-12-20
Proof-of-concept repository on GitHubstars:02023-05-15

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+62 d
  3. TodayOct 26, 2026+1468 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records