dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-48386

MEDIUM · 6.3 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Git's wincred credential helper on Windows uses a static buffer (target) as a unique key for credential storage and comparison. The code does not properly bounds-check available space before appending to this buffer using wcsncat(), allowing potential buffer overflows when credential data exceeds the buffer size.

MitigationUpgrade Git to version v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1. This is a medium-severity issue affecting Windows credential handling workflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows environment
    Verify the operating system is Windows. Run 'uname -s' or check system properties. The wincred helper only exists on Windows.
    Affected if The system is running Windows with Git installed.
  2. Identify Git version
    Run 'git --version' to obtain the installed Git version number.
    Affected if The installed version is earlier than v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1 in their respective release branches.
  3. Check credential helper configuration
    Run 'git config --global credential.helper' to see which credential helper is configured. Also check 'git config --global credential.<name>.helper' for any helper-specific settings.
    Affected if The configured credential helper is 'wincred' or uses the Windows credential storage subsystem.
  4. Verify wincred is in use
    Inspect Git configuration files (global: %USERPROFILE%\.gitconfig or ~/.gitconfig on Windows) for entries under the [credential] section that reference wincred or Windows credential storage.
    Affected if The [credential] section in Git config specifies wincred as the helper or relies on default Windows credential handling.

A user is affected if they are on Windows, running a Git version earlier than the fixed releases, and have wincred or Windows credential handling enabled as the Git credential helper.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Git to version v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1. This is a medium-severity issue affecting Windows credential handling workflows.

Recommended fix High confidence

v2.50.1 (or latest patch version of your current release branch)

  1. 1. Determine the current Git version by running: git --version
  2. 2. Identify which release branch your current version belongs to (e.g., v2.43.x, v2.44.x, v2.45.x, etc.)
  3. 3. Upgrade Git to the latest patch release for your release branch, or upgrade to the latest stable release v2.50.1
  4. 4. On Windows: Download and install the latest Git for Windows from git-scm.com or use a package manager like winget (winget install Git.Git), Chocolatey (choco upgrade git), or Scoop (scoop update git)
  5. 5. On Linux: Use your distribution's package manager (e.g., apt-get update && apt-get upgrade git, yum update git, dnf update git, etc.)
  6. 6. On macOS: Use Homebrew (brew upgrade git) or MacPorts (sudo port upgrade git)
  7. 7. Verify the upgrade was successful by running: git --version
  8. 8. Confirm the installed version is one of the fixed releases: v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48386 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data