CVE-2025-48384
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Git allows arbitrary code execution through broken config quoting
rank 76 = 40 + 20 + 0 + 8 + 8
rank@v1 · act now
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.04109 · CISA KEV listed · without this subject the record ranks 36
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 8.1, from the CNA · without this subject the record ranks 56
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 76
How much of the world it touches
NVD CPE configurations
10 products in the CPE ranges · without this subject the record ranks 68
Someone else already set the date
CISA KEV remediation due date
CISA remediation date held · without this subject the record ranks 68
$205,000 = $4.99M incident cost x 1 exposure x 0.04109 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.
Running git? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Exploited in the wild · CISA KEV listed, 2025-08-25.
Affected & Fixed Versions as published
Show all 10 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
Attack path
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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.
NVD's analysis a second authority
- weakness
- CWE-59; CWE-436
- affected versions
- git-scm git < 2.43.7; git-scm git >= 2.44.0 < 2.44.4; git-scm git >= 2.45.0 < 2.45.4; and 7 more, listed in full below
- also scored by
- [email protected] 8 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
check it yourself github.com receipt
Dated events
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 58 observations
58 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
Listed by CISA 48 days after it published, exploit probability more than doubled between 2025-11-17 and 2025-11-18 (0.01461 → 0.03193) and the record had been public for 1 year, 1 month when this index was last written.
No material movement in 19 days as of the last ingest this index recorded.
Siblings and hubs
Records related to this one
No record cites this identifier and it carries no alias. Its defect family is below.
Its defect family
git
Of the 6 records in this family, this is the only one with public proof-of-concept code, and it holds 43 references to it.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Family membership: computed, pro@dim2000
This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.
Browse the index from here
These are index-wide views, not findings about CVE-2025-48384.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.