Threats / Git / CVE-2025-48384
CVE-2025-48384
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Git vulnerability
Git contains a link following vulnerability due to inconsistent handling of carriage return characters in configuration files, enabling local privilege escalation or arbitrary code execution.
Verdict
Today item — known-exploited.
A local attacker can exploit improper carriage return handling in Git configuration parsing to follow symlinks or access unintended files, potentially executing arbitrary code or escalating privileges on systems where Git processes untrusted configuration.
CISA KEV Yes · 2025-08-255EPSS 0.04109 (verify live)6Exploit Public PoC7CVSS 8.13CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-08-25).
Probability (EPSS)
EPSS 0.04109 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H) · Affected: Git, Git. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-436 CWE-436, CWE-59 Link Following — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 48 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Git configuration file with embedded carriage return characters to bypass path validation checks.
Business
An attacker gains the ability to manipulate Git's file access behavior, creating a foothold for code execution on developer workstations or CI/CD systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I place a symlink in a location where Git's carriage return handling causes it to follow the link to a sensitive system file.
Business
Sensitive configuration data or system files become accessible to unprivileged processes, exposing credentials or enabling further compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the file access to inject malicious commands into Git hooks or configuration that execute with the privileges of the Git process.
Business
Arbitrary code execution occurs in the context of the user running Git, potentially compromising development environments, build pipelines, or production deployments.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by GitHub_MCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.