GitApplication · Git Scm
CVE-2025-48384
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 · uneditedGit 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.
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 confidenceGit has a CRLF handling vulnerability where trailing carriage return characters in submodule paths cause incorrect path resolution during checkout. When a submodule path contains a trailing CR, Git reads an altered path causing checkout to an incorrect location. If a symlink points this altered path to the submodule hooks directory and an executable post-checkout hook exists, it can be unintentionally executed, leading to arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitApplication
< 2.43.7>= 2.44.0, < 2.44.4>= 2.45.0, < 2.45.4>= 2.46.0, < 2.46.4>= 2.47.0, < 2.47.3>= 2.48.0, < 2.48.2>= 2.49.0, < 2.49.1>= 2.50.0, < 2.50.1
Debian LinuxOperating system
= 11.0< 26.0CVSS 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
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Git versionRun `git --version` and compare the output to the affected version ranges: < 2.43.7; >= 2.44.0, < 2.44.4; >= 2.45.0, < 2.45.4; >= 2.46.0, < 2.46.4; >= 2.47.0, < 2.47.3; >= 2.48.0, < 2.48.2; >= 2.49.0, < 2.49.1; >= 2.50.0, < 2.50.1Affected if The installed version falls within any of the affected ranges
-
Inspect submodule paths for trailing CR charactersExamine the .gitmodules file and run `git submodule status` to identify submodules. Use a hex viewer or grep with non-printable character detection (e.g., `grep -P '\r' .gitmodules` or `git config --get-regexp submodule\..*\.path` with output inspected for CR bytes at line ends) to detect trailing carriage return characters in submodule pathsAffected if Any submodule path contains a trailing CR (\r) character before the line break
-
Look for symlinks pointing to hooks directoriesSearch the repository for symlinks that resolve to paths containing 'hooks' (e.g., `find . -type l -ls` and inspect target paths, or search for symlinks with 'hooks' in the target using `find . -type l -exec ls -la {} \; 2>/dev/null | grep -i hooks`)Affected if A symlink target contains 'hooks' and points to an unexpected location or a location within a submodule directory
-
Identify executable post-checkout hooks in submodulesSearch for post-checkout hook files within submodule directories and check their permissions: `find . -path '*/.git/hooks/post-checkout' -type f -executable` or within submodule paths, and examine any hook that exists in directories reachable via symlinks from step 3Affected if An executable post-checkout hook exists in a location that could be triggered through the symlink misdirection caused by trailing CR in submodule paths
You are affected if your Git version is within the vulnerable ranges AND you have submodules with trailing CR characters in their paths, combined with suspicious symlinks that could redirect execution to executable hooks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.43.72.44.42.45.4
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. Additionally, audit repositories for submodule configurations involving paths with special characters and symlinks pointing to hooks directories.
Git 2.46.4 (or 2.47.3/2.48.2/2.49.1/2.50.1 for latest stable)
- Check current Git version by running: git --version
- Identify your current version branch: if < 2.43.7 upgrade to 2.43.7 or later; if >= 2.44.0 and < 2.44.4 upgrade to 2.44.4 or later; if >= 2.45.0 and < 2.45.4 upgrade to 2.45.4 or later; if >= 2.46.0 and < 2.46.4 upgrade to 2.46.4 or later
- On Linux/Debian: run 'apt-get update && apt-get install git' to get the latest packaged version
- On macOS with Homebrew: run 'brew upgrade git'
- On Windows: download installer from git-scm.com or update via Git for Windows
- Verify upgrade succeeded: run 'git --version' and confirm it shows a fixed version (2.43.7+, 2.44.4+, 2.45.4+, 2.46.4+, or later)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Git
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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