Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-48384: Git allows arbitrary code execution through broken config quoting

Noroxi assessment

Priority: This week (action score 63/100)

  • CISA has confirmed exploitation in the wild (Aug 25, 2025). Remediation deadline for US federal agencies: Sep 15, 2025.
  • Probability of exploitation in the next 30 days: 4.3% (FIRST EPSS); higher than 91.2% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.75; Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.49; Microsoft Visual Studio 2022 version 17.10 17.10.17.

Don’t wait for the next maintenance window. Upgrade to Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.75; Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.49; Microsoft Visual Studio 2022 version 17.10 17.10.17 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 · CISA KEV · FIRST EPSS

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

HighCVSS 8.0 · v3.1KEVWeaponized Fix available
Published
Jul 8, 2025
Updated
Sep 24, 2026
EPSS
4.3% · 91th percentile

Report tools

JSON

Action score

63

This week

Don’t wait for the next maintenance window.

CVSS
32 / 40 · 8.0 / 10
CISA KEV
30 / 30 · Listed
EPSS
1 / 30 · 4.3%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
8.1
NVD has not scored this yet; the score shown is the CNA’s.

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

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Aug 25, 2025. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Sep 15, 2025.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

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

Follow CVE-2025-48384

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for git-scm records

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
debiandebian linux
applexcode

Affected versions

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

  • apple xcodebefore 26.0
  • debian debian linux11.0
  • git-scm git2.45.0 and later · before 2.45.4
  • git-scm git2.46.0 and later · before 2.46.4
  • git-scm git2.47.0 and later · before 2.47.3
  • git-scm gitbefore 2.43.7
  • git-scm git2.49.0 and later · before 2.49.1
  • git-scm git2.50.0 and later · before 2.50.1
  • git-scm git2.48.0 and later · before 2.48.2
  • git-scm git2.44.0 and later · before 2.44.4

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.43.7, >= 2.44.0-rc0, < 2.44.4, >= 2.45.0-rc0, < 2.45.4, >= 2.46.0-rc0, < 2.46.4, >= 2.47.0-rc0, < 2.47.3, >= 2.48.0-rc0, < 2.48.2, >= 2.49.0-rc0, < 2.49.1, >= 2.50.0-rc0, < 2.50.1affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10git-allbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-core-docbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-emailbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-guibefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-instawebbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-subtreebefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10git-svnbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10gitkbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10gitwebbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10perl-Gitbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:10perl-Git-SVNbefore 2.47.3-1.el10_02.47.3-1.el10_0
AlmaLinux:8gitbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-allbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-corebefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-core-docbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-credential-libsecretbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-daemonbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-emailbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-guibefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-instawebbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-subtreebefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8git-svnbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8gitkbefore 2.43.7-1.el8_102.43.7-1.el8_10
AlmaLinux:8gitwebbefore 2.43.7-1.el8_102.43.7-1.el8_10

+96

Same product

git-scm: all records

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-2021-21300malicious repositories can execute remote code while cloning
    60This week
  • CVE-2017-1000117A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any prog
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2024-32020May 14, 2024 · Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will
    13Monitor
  • ← EarlierCVE-2024-32021May 14, 2024 · Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory
    28Monitor
  • ← EarlierCVE-2024-32465May 14, 2024 · Git's protections for cloning untrusted repositories can be bypassed
    31Monitor

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
Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)15.9.75 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)16.11.49 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1017.10.17 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1217.12.10 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1417.14.8 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.817.8.23 · Release NotesMicrosoft (MSRC)
almalinux:git2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.47.3-1.el9_6 · AlmaLinux:9Package registry (OSV)
alpine:git2.43.7-r0 · Alpine:v3.19Package registry (OSV)
debian:git1:2.39.5-0+deb12u3 · Debian:12Package registry (OSV)
opensuse:git2.51.0-150600.3.12.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:git-lfs3.7.0-150600.13.3.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:obs-scm-bridge0.7.4-150600.14.4.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python-PyYAML6.0.2-150600.10.3.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:git0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-all0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret0:2.47.3-1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+11

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Proof-of-concept repository on GitHub ×42

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:522025-07-08
Proof-of-concept repository on GitHubstars:02025-07-09
Proof-of-concept repository on GitHubstars:02025-07-09
Proof-of-concept repository on GitHubstars:02025-07-09
Proof-of-concept repository on GitHubstars:02025-07-09
Proof-of-concept repository on GitHubstars:212025-07-09
Proof-of-concept repository on GitHubstars:02025-07-09
Proof-of-concept repository on GitHubstars:02025-07-10
Proof-of-concept repository on GitHubstars:02025-07-10
Proof-of-concept repository on GitHubstars:02025-07-10
Proof-of-concept repository on GitHubstars:02025-07-10
Proof-of-concept repository on GitHubstars:02025-07-10

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. First PoC-1 d
  2. Published
  3. CISA KEV+47 d
  4. TodayOct 30, 2026+479 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.

Credits

All researchers

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

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records