- Cisa adds the CVE-2025-48384 to its catalog of known vulnerabilities known
- Git corrected it in July 2025, but there are also attenuations and bypass solutions
- Users must patcher immediately or cope with a possible attack
The American Cybersecurity and Infrastructure Safety Agency (CISA) has added a serious vulnerability of the GIT to its known catalog of exploited vulnerabilities (KEV), warnings of abuse in jumps and giving the federal agencies of the Directorate of the Civil Executive (FCEB) three weeks to be accompanied.
The Git distributed version control system is a software development tool helping users keep trace of code changes, allowing them to share it with others and cooperate on different projects.
He was recently discovered that he had a bug where he manages the special “return by car” characters in an incoherent manner – so when configuring the submoxles, this can encourage Git to configure a repository in the wrong place, then to execute a hidden code and provided by the attacker.
Avoid recursive submodle clones
The bug is followed 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 Distributed version control system: 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. This is the standard version control system used by developers around the world, and platforms like Github, Gitlab and Bitbucket work on Git. In addition, almost all the main software projects, including Linux, Android, Chrome and VS Code, use it to manage the code.
When Cisa adds a bug to Kev, it generally means that he observed that he was used in real attacks. This flaw was added on July 25, 2025, which means that FCEB agencies have until September 15 to repair it or stop using Git completely. Usually other government agencies, as well as private sector companies, also follow KEV and apply updates at the same time.
Those who are unable to patcher can deploy attenuation in the form of avoiding recursive submodle clones from unreliable sources. In addition, users must deactivate Git hooks worldwide via core.Hookspath and only apply audited submodles.
Via Bleeping Compompute
