- CISA adds CVE-2025-48384 to its catalog of known exploited vulnerabilities
- Git patched him in July 2025, but there are also mitigations and solutions.
- Users must immediately patch or face a possible attack
The United States Cybersecurity and Infrastructure Security Agency (CISA) has added a serious git vulnerability to its well-known catalog of exploited vulnerabilities (KEV), warning about the abuse in-the blessed and grants the Federal Executive Executive Branch agencies (FCEB) three weeks to repair.
The GIT distributed version control system is a software development tool that helps users to monitor changes in the code, which allows them to share it with others and cooperate in different projects.
Recently it was discovered that it had an error in which it handles special characters of “car return” in an inconsistent way, so when configuring submodules, this can deceive the configuration of a repository in the incorrect place and then execute the hidden code and supplied by the attacker.
Avoid clones of recursive submodules
The error is tracked as CVE-2025-48384, and has a gravity score of 8.0/10 (high). It was discovered in early July 2025 and set with a patch. Here is a list of the distributed version control system Git Path: 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1 and 2.50.1.
Git is extremely popular. It is the standard version control system used by developers around the world, and platforms such as Github, Gitlab and Bitbucket are executed in Git. In addition, almost all important software projects, including Linux, Android, Chrome and VS Code, use it to administer the code.
When CISA adds an error to Kev, it generally means that it has observed that it is used in real -life attacks. This defect was added on July 25, 2025, which means that FCEB agencies have until September 15 to repair or stop using git completely. In general, other government agencies, as well as companies in the private sector, monitor Kev and apply updates at the same time.
Those who cannot patch can implement a mitigation in the way of avoiding clones of recursive submodules of non -reliable sources. In addition, users should disable Hooks gits worldwide through CORE. HookSPath, and enforce only audited submodules.
Through Bleepingcomputer
