Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114094 Overview
CVE-2026-114094 is an arbitrary file write vulnerability in Dulwich, a pure-Python implementation of the Git file formats and protocols. Versions prior to 1.2.9 fail to validate DOS drive letter prefixes in Git tree path elements on Windows. An attacker who publishes a malicious repository can include a tree entry named C: that bypasses existing NTFS path validation. When a Windows user clones or checks out the repository, Dulwich writes files outside the worktree. Writing to startup or auto-run locations enables remote code execution. The flaw is tracked under CWE-22: Path Traversal.
Critical Impact
A crafted Git repository can write arbitrary files outside the worktree on Windows hosts running Dulwich, leading to remote code execution upon clone or checkout.
Affected Products
- Dulwich versions prior to 1.2.9
- Windows platforms using Dulwich for Git operations
- Downstream tooling that embeds Dulwich as a Git client library
Discovery Timeline
- 2026-10-21 - CVE-2026-114094 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-114094
Vulnerability Analysis
Dulwich implements Git tree parsing and worktree checkout in pure Python. During checkout, each tree entry name is combined with the worktree root to produce the destination path. On Windows, path resolution respects DOS drive letter prefixes such as C:relative\path and absolute forms like C:\Windows. Dulwich's prior sanitation routine rejected path separators and reserved NTFS names but did not treat a bare drive letter such as C: as an absolute reference. An attacker commits a tree entry whose name contains or begins with a drive letter prefix. When the victim checks out the repository, Python's path join on Windows discards the worktree prefix and resolves against the attacker-controlled drive location.
Root Cause
The root cause is incomplete input validation on tree entry names during worktree materialization. The sanitizer blocked traversal sequences and NTFS reserved names but omitted DOS drive letter semantics unique to the Windows path parser. This mismatch between Git tree semantics and Windows path resolution allows path traversal outside the intended worktree.
Attack Vector
Exploitation requires a victim to interact with a malicious repository using Dulwich on Windows. Typical delivery is a public clone target, a submodule, or a package pulled by developer tooling. User interaction is required, consistent with the CVSS vector component UI:P. Once checkout runs, the attacker chooses the destination path. Writing an executable or shortcut into the per-user Startup folder yields code execution at next logon. The vulnerability is network-reachable because the malicious repository is distributed over Git transports.
See the GitHub Security Advisory GHSA-8mcx-5rqc-vhmf and the VulnCheck Advisory for additional technical details. No verified public proof-of-concept code is available at this time.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-114094
Indicators of Compromise
- Files created outside the expected worktree root on Windows systems that recently ran a Dulwich clone, pull, or checkout operation.
- New or modified files in sensitive locations such as %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup after Git operations.
- Git tree objects containing entry names that include a colon character or begin with a drive letter such as C:.
Detection Strategies
- Scan Git repositories and mirrors for tree entries whose names match the regular expression ^[A-Za-z]: or contain a colon.
- Monitor Python processes importing dulwich for file write operations with destination paths that fall outside the active worktree.
- Audit developer endpoints for installed Dulwich versions below 1.2.9 using package inventory tools.
Monitoring Recommendations
- Alert on file creation in auto-run and Startup directories where the parent process is python.exe or a Dulwich-based tool.
- Log and review all clone and fetch operations against external or untrusted Git remotes on Windows build hosts.
- Correlate newly written persistence artifacts with recent Git activity in endpoint telemetry.
How to Mitigate CVE-2026-114094
Immediate Actions Required
- Upgrade Dulwich to version 1.2.9 or later on all Windows systems and build agents.
- Inventory applications and CI pipelines that embed Dulwich as a dependency and schedule rebuilds against the patched release.
- Restrict Git clone and fetch operations to trusted remotes until patching is complete.
Patch Information
The maintainers released Dulwich 1.2.9 with input validation that rejects tree entry names containing DOS drive letter prefixes on Windows. Install the fixed release with pip install --upgrade "dulwich>=1.2.9". Downstream distributions should pull in the corresponding package update. Review the GitHub Security Advisory GHSA-8mcx-5rqc-vhmf for the exact commit and release notes.
Workarounds
- Avoid using Dulwich on Windows for untrusted repositories until the upgrade is applied.
- Run Git operations inside an isolated container or sandboxed account with no write access to persistence paths.
- Pre-scan incoming repository tree objects and reject entries whose names contain a colon or match a drive letter pattern.
# Upgrade Dulwich to the patched release
pip install --upgrade "dulwich>=1.2.9"
# Verify the installed version
python -c "import dulwich; print(dulwich.__version__)"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

