CVE-2026-52726: Dulwich Git Submodule Path Traversal & RCE

Technical summary

The vulnerability stems from insufficient path validation in `dulwich.porcelain.submodule_update()` and the recursive submodule cloning path invoked by `porcelain.clone(..., recurse_submodules=True)`. A crafted `.gitmodules` configuration combined with a corresponding tree gitlink entry specifying a malicious path (e.g., `.git/hooks/pre-commit`) allows an attacker to materialize submodule contents directly into sensitive directories within the parent repository's `.git` folder. The dropped files retain executable permissions, enabling arbitrary command execution when Git or Dulwich invokes the corresponding hook during subsequent operations. This mirrors the upstream Git security fixes for CVE-2024-32002 and CVE-2024-32004, which were not applied to Dulwich's independently maintained submodule handling logic.

Business impact

Organizations and developers using Dulwich to automate repository operations—particularly in CI/CD pipelines, deployment workflows, or automated repository management tools—face significant risk. Successful exploitation results in arbitrary code execution within the context of the process running Dulwich, potentially compromising build systems, credentials, source code, or downstream deployments. The attack requires no user interaction beyond cloning or updating a repository, making it particularly dangerous in unattended automation scenarios where an attacker can poison an upstream repository or perform supply-chain attacks.

Affected systems

Dulwich versions 0.23.2 through 1.2.4 are vulnerable. Any system or application using these versions to clone or update Git repositories with submodules enabled is at risk, particularly in CI/CD environments, automated deployment tools, and developer workstations that interact with untrusted or publicly accessible repositories.

Exploitability

Exploitation is straightforward and requires only network access to deliver a malicious repository. No authentication, special user privileges, or user interaction is needed beyond initiating a clone or submodule update operation. The attack surface is broad: any automated tool, script, or service that pulls code from repositories without strict repository signing or validation mechanisms is vulnerable. The ease of exploitation and lack of defensive friction make this a practical threat.

Remediation

Upgrade Dulwich to version 1.2.5 or later immediately. This version implements proper path validation to prevent submodules from being materialized outside the repository's working tree or into sensitive `.git` subdirectories. After patching, audit any recent repository clones or submodule updates performed with vulnerable Dulwich versions to detect and remove potentially malicious hook files from your `.git/hooks/` directories.

Patch guidance

Update Dulwich via your package manager (e.g., `pip install --upgrade dulwich>=1.2.5` for Python environments). Verify the installed version using `pip show dulwich` or equivalent. If Dulwich is a transitive dependency of another tool, ensure that tool and its dependencies are also updated to pull in the patched Dulwich version. Test the upgrade in a non-production environment first, particularly if Dulwich integration is critical to your workflows.

Detection guidance

Search your `.git/hooks/` directory for recently created or modified executable files, especially those with names suggesting they were not created by your team (look for timestamps correlating with suspicious repository clones or updates). Review repository clone and pull logs from the time period when vulnerable Dulwich versions were in use. If using Git, check `git log --all` for unexpected submodule entries pointing to `.git/*` paths in `.gitmodules`. Implement Git hook integrity monitoring in sensitive repositories to detect unauthorized modifications.

Why prioritize this

This vulnerability merits immediate remediation due to its high severity (CVSS 7.5), complete lack of authentication requirements, straightforward exploitation path, and impact on supply-chain security. Automated systems relying on Dulwich are particularly exposed. The fact that this mirrors known upstream Git vulnerabilities (CVE-2024-32002, CVE-2024-32004) that have been actively exploited reinforces urgency.

Risk score, explained

The CVSS 7.5 (HIGH) score reflects network-accessible exploitation (AV:N), low complexity (AC:L), no privilege or user interaction requirements (PR:N/UI:N), and denial-of-service impact (A:H). However, the actual risk is substantially elevated by the arbitrary code execution capability—which the CVSS vector does not fully capture—combined with prevalence in automation and CI/CD contexts where a single compromise can cascade to multiple systems.

Frequently asked questions