✨
Échantillon de contenu généré par l'IA de BlogFlow Secteur : Cybersécurité · Conçu pour générer du trafic qualifié sur Google
Obtenir ces articles sur mon site →
Cybersécurité • • 519 mots

A Critical Git Vulnerability and How to Stay Secure

A recent Git vulnerability allows malicious code execution during recursive clones. Learn how to protect your systems and what steps to take now.

A Major Security Flaw in Git Has Been Fixed

A critical vulnerability in Git has been addressed in the latest updates, preventing malicious repositories from executing code on users' systems during recursive clones. This flaw, identified as CVE-2026-111760, was fixed in Git 2.56.1 and earlier versions such as 2.50.2, 2.51.3, and others. The vulnerability stemmed from an integer truncation issue in how Git handles repository paths.

How the Vulnerability Worked

The flaw allowed attackers to exploit a specific weakness in Git's handling of long file paths. If a malicious repository contained an extremely long path, Git would write it to disk under a shorter name. Attackers could then manipulate this to point to a .git file, which Git would then use to execute malicious code through hooks or configuration files.

Submodules were a key factor in this vulnerability. Normally, Git prevents replacing a .git folder with a symbolic link, but in a freshly cloned submodule, .git is a file. This made it easier for attackers to inject malicious code into the system.

What Has Been Done to Fix the Issue

The Git project has released updated versions that now reject extremely long paths before they can be truncated. This change prevents the vulnerability from being exploited. GitHub, which uses Git in its tools, has also applied the fix to its platforms, including GitHub.com and GitHub Enterprise Cloud.

For users who rely on Git, the recommendation is to update to the latest version of Git from your operating system or Git distributor. GitHub has also released updated versions of its desktop and Copilot apps, with more updates coming for Codespaces and GitHub Actions.

Additional Security Fixes in the Update

Alongside the main vulnerability, the update also addressed five other flaws, including:

  • CVE-2026-113408: A malicious server could send a branch name with path traversal, allowing writes outside Git's reference folder.
  • CVE-2026-114467: Merging a tag with more than two GPG signatures could corrupt memory and cause a denial of service.
  • CVE-2026-114469: A very large binary patch could bypass Git's size limit and crash the system.
  • CVE-2026-105437: A large merge with many conflicts could corrupt memory.
  • CVE-2026-114466: Certain Git fast-import features could be used to read or create arbitrary files.

What You Can Do to Stay Secure

Until you can update to the latest version of Git, GitHub recommends the following steps:

  • Clone repositories only from trusted servers.
  • Avoid recursively cloning repositories you don't trust.
  • Do not merge content or tags from untrusted sources.
  • Avoid processing binary patches or fast-import streams from untrusted sources.

These steps are not a replacement for the updates but can help reduce the risk of exploitation.

Why This Matters for Your Business

As a business, ensuring that your development tools are up to date is crucial. This vulnerability could have allowed attackers to inject malicious code into your systems, potentially leading to data breaches or system compromises. By staying informed and taking action, you can protect your company's data and operations.

{{appel_action}}


Source : The Hacker News

Mots-clés : #cybersecurity #git security #software vulnerabilities
Auteur / Émetteur

Découvrez comment BlogFlow peut automatiser la rédaction de votre blog d'entreprise.

Essai 7 jours gratuit