What it is
CVE-2025-48384 is a vulnerability affecting git. 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....
Vulnerability report
git
Git · affected before 2.43.7
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2025-48384 is a vulnerability affecting git. 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....
Is it exploited?
Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV. Also confirmed by third-party sources.
Who is affected?
git affected before 2.43.7.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
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.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CVE
A trusted third party reported exploitation.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CVE First | 2026-06-01 10:39 UTC |
| CISA | 2026-06-02 14:06 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
4.4%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Timeline
14:06 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
10:39 UTC
High-confidence, third-party attested exploitation
18:23 UTC
Vulnerability disclosed publicly
15:46 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2025-48384
Free JSON includes basic KEV fields{
"cve_id": "CVE-2025-48384",
"confidence": "Confirmed",
"cvss_score": 8.0,
"cvss_estimated": false,
"epss_score": 0.04379,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}