<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Directory Modification — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/directory-modification/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 28 May 2026 07:25:12 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/directory-modification/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-45571 go-git Crafted Repositories Modify .git Directories</title><link>https://feed.craftedsignal.io/briefs/2026-05-go-git-dir-mod/</link><pubDate>Thu, 28 May 2026 07:25:12 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-go-git-dir-mod/</guid><description>CVE-2026-45571 is a vulnerability in go-git that allows crafted repositories to modify main and submodule .git directories, potentially leading to arbitrary code execution or information disclosure.</description><content:encoded><![CDATA[<p>CVE-2026-45571 is a critical vulnerability affecting the go-git library, a popular Go implementation of Git. This flaw allows a malicious actor to craft a Git repository that, when processed by a vulnerable application using go-git, can modify the <code>.git</code> directories of both the main repository and its submodules. This modification could be leveraged to overwrite configuration files, inject malicious Git hooks, or otherwise compromise the integrity of the repository and the system on which it resides. Successful exploitation could lead to arbitrary code execution or sensitive information disclosure. Defenders should prioritize identifying and mitigating applications utilizing vulnerable versions of go-git.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts a malicious Git repository containing specially crafted files or symbolic links designed to manipulate <code>.git</code> directories.</li>
<li>A user or automated system clones or interacts with the malicious repository using a vulnerable version of go-git.</li>
<li>The vulnerable go-git library processes the malicious repository content without proper validation or sanitization.</li>
<li>The crafted content overwrites or modifies configuration files within the main repository&rsquo;s <code>.git</code> directory.</li>
<li>The crafted content also propagates to any submodules present, modifying their respective <code>.git</code> directories.</li>
<li>The modification of <code>.git</code> directories allows the attacker to inject malicious Git hooks (e.g., pre-commit, post-receive).</li>
<li>When a user performs Git operations (e.g., commit, push, pull), the injected malicious hooks are executed.</li>
<li>The malicious hooks execute arbitrary code, potentially leading to complete system compromise or data exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-45571 can have severe consequences. An attacker could gain arbitrary code execution on systems using vulnerable versions of go-git. This could lead to data breaches, system compromise, and denial-of-service attacks. The vulnerability poses a significant risk to organizations that rely on go-git for managing source code, configuration files, or other sensitive data within Git repositories. The lack of specific victim count data makes assessing the total impact difficult, but the wide usage of go-git implies a potentially broad attack surface.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade go-git to a patched version that addresses CVE-2026-45571.</li>
<li>Implement the Sigma rule &ldquo;Detect Go-Git .git Directory Modification&rdquo; to detect potential exploitation attempts in real-time.</li>
<li>Review and audit existing Git repositories for suspicious files or symbolic links that could be used to exploit this vulnerability.</li>
<li>Monitor file system events within <code>.git</code> directories using the Sigma rule &ldquo;Detect Git Hook Creation in .git Directory&rdquo; to identify unauthorized modifications.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve</category><category>go-git</category><category>git</category><category>directory modification</category><category>code execution</category></item></channel></rss>