Git Patches Flaw Letting Bad Repos Run Code
Git Patches Flaw Letting Bad Repos Run Code
Git Patches Flaw Letting Bad Repos Run Code
Key points
اہم نکات
मुख्य बातें
- A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1.
- The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs.
- The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems.
- A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1.
- The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs.
- The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems.
- A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1.
- The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs.
- The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems.
A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1. The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs. The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems. Until a fixed version is installed, GitHub advises cloning only from trusted servers and avoiding recursive clones of repositories you do not trust.
A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1. The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs. The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems. Until a fixed version is installed, GitHub advises cloning only from trusted servers and avoiding recursive clones of repositories you do not trust.
A flaw in Git could let a booby-trapped repository run an attacker's code on your computer during a recursive clone, and the fix is out now in Git 2.56.1. The flaw, CVE-2026-111760, rated High with a CVSS score of 8.0, comes from an integer truncation in how Git handles its index: an extremely long path can pass Git's safety checks under one name and then be written under a shorter name, letting an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration that Git then runs. The Git project fixed six flaws in total on November 10, with backports to versions 2.50.2 through 2.55.1, and GitHub says it has already patched its own systems. Until a fixed version is installed, GitHub advises cloning only from trusted servers and avoiding recursive clones of repositories you do not trust.
Most read
سب سے زیادہ پڑھی گئی
सबसे ज़्यादा पढ़ी गई
- Loading...
Get news in your inbox
خبریں اپنے ان باکس میں حاصل کریں
खबरें अपने इनबॉक्स में पाएं
One email when new stories are published. No spam, unsubscribe anytime.
نئی خبریں شائع ہونے پر ایک ای میل۔ کوئی سپیم نہیں، کسی بھی وقت ان سبسکرائب کریں۔
नई खबरें प्रकाशित होने पर एक ईमेल। कोई स्पैम नहीं, कभी भी अनसब्सक्राइब करें।