NVD / CVE Program· CNA GitHub_M

CVE-2025-48386: Git allows a buffer overflow in 'wincred' credential helper

Noroxi assessment

Priority: Monitor (action score 25/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
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: 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.

Low priority for now. 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 · 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. The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows. 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.

MediumCVSS 6.3 · v3.1—No exploit Fix available

Memory safety

Published: Jul 8, 2025
Updated: Jun 17, 2026
EPSS: 0.4% · 37th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.3; 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.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

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

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.

—

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.

Ecosystem	Package	Affected range	Fix
Alpine:v3.19	git	before 2.43.7-r0	2.43.7-r0
Alpine:v3.20	git	before 2.45.4-r0	2.45.4-r0
Alpine:v3.21	git	before 2.47.3-r0	2.47.3-r0
Alpine:v3.22	git	before 2.49.1-r0	2.49.1-r0
Alpine:v3.23	git	before 2.50.1-r0	2.50.1-r0
openSUSE:Tumbleweed	git	before 2.50.1-1.1	2.50.1-1.1
SUSE:Linux Micro 6.0	git	before 2.51.0-1.1	2.51.0-1.1
SUSE:Linux Micro 6.1	git	before 2.51.0-slfo.1.1_1.1	2.51.0-slfo.1.1_1.1

Same product

git: all records

Other highest-scoring records for the same primary product.

CVE-2024-32002Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
45Plan
CVE-2022-25648The package git before 1.11.0 are vulnerable to Command Injection via git argument injection.
40Plan
CVE-2025-48385Git alllows arbitrary file writes via bundle-uri parameter injection
34Monitor

Published before and after this one in the same product

← EarlierCVE-2024-50349Jan 14, 2025 · Git does not sanitize URLs when asking for credentials interactively
8Monitor
← EarlierCVE-2024-52006Jan 14, 2025 · Newline confusion in credential helpers can lead to credential exfiltration in git
8Monitor
← EarlierCVE-2024-52005Jan 15, 2025 · The sideband payload is passed unfiltered to the terminal in git
30Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)	15.9.75 · Release Notes	Microsoft (MSRC)
Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)	16.11.49 · Release Notes	Microsoft (MSRC)
Microsoft Visual Studio 2022 version 17.10	17.10.17 · Release Notes	Microsoft (MSRC)
Microsoft Visual Studio 2022 version 17.12	17.12.10 · Release Notes	Microsoft (MSRC)
Microsoft Visual Studio 2022 version 17.14	17.14.8 · Release Notes	Microsoft (MSRC)
Microsoft Visual Studio 2022 version 17.8	17.8.23 · Release Notes	Microsoft (MSRC)
alpine:git	2.43.7-r0 · Alpine:v3.19	Package registry (OSV)
opensuse:git	2.50.1-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
suse:git	2.51.0-1.1 · SUSE:Linux Micro 6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

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

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

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

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

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

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

nvd-secondary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

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

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

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

References

github.com/git/git/security/advisories/GHSA-4v56-3xvj-xvfr

Show all references (1 more)

www.openwall.com/lists/oss-security/2025/07/08/4

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

All records