NewsCompaniesFlawsGuides
Get the app

CVE-2025-48384

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Git. For every flaw being used in attacks, see Exploited flaws.

CVE-2025-48384 is a security flaw in Git. Attackers are using a flaw in Git. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 25 Aug 2025.[1]

Git is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Git has published a fix or advice.

Description

CISA calls it a link following in Git Git. In its words: “Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is CWE-59, CWE-436, in MITRE’s list of common software weaknesses.

It scores 8.0 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Git’s advisory has them[3]. CISA names the product as Git Git.

Most families won’t have Git; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 25 Aug 2025, 48 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 15 Sep 2025 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 4%. That’s in the top 9% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Git has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Git is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 15 Sep 2025 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.0.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 4%.[4]

See also

Similar flaws

  • CVE-2026-81963, Microsoft Windows: link following ·
  • CVE-2015-5287, Red Hat Automatic Bug Reporting Tool: privilege escalation ·
  • CVE-2026-41091, Microsoft Defender: link following ·
  • CVE-2025-60710, Microsoft Windows: link following ·
  • CVE-2025-21391, Microsoft Windows: storage link following ·

Added the same day

  • CVE-2024-8069, Citrix Session Recording: deserialization of untrusted data ·
  • CVE-2024-8068, Citrix Session Recording: improper privilege management ·

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Git Link Following Vulnerability”. Known Exploited Vulnerabilities Catalog, added 25 Aug 2025.
  2. ^ National Institute of Standards and Technology. “CVE-2025-48384 Detail”. National Vulnerability Database, published 8 Jul 2025.
  3. ^ Git. Advisories and fixes: github.com, access.redhat.com, alas.aws.amazon.com, linux.oracle.com, msrc.microsoft.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.044, percentile 91.3, 31 Oct 2026.
  5. CVE Program. “CVE-2025-48384”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.