The vulnerability in Dulwich allows an attacker who can supply a malicious Git repository to perform an arbitrary file write on Windows systems. When a user clones, fetches, or checks out such a repository, the path‑element validator improperly accepts filenames containing NTFS‑specific structural characters, enabling the repository’s tree entries to overwrite files in the local repository directory. This write can then be used to execute malicious code, resulting in full remote code execution on the affected machine. The weakness is a path traversal error, mapped to CWE‑22, and is exploitable without requiring elevated privileges if the user has write permission to the target location.

The issue affects all Dulwich installations from early releases up through version 1.2.4, inclusive. The vendor is jelmer:dulwich, which provides a pure‑Python implementation of Git for Python applications. Upgrading to Dulwich 1.2.5 or later removes the vulnerability, as the NTFS validator is enabled by default on every platform in that and later releases.

The CVSS score of 8.8 signals high severity, and the vulnerability is present on Windows machines whenever a user interacts with a malicious repository through any Dulwich‑based tool. Although the EPSS score is not available, the lack of a known workaround and the nature of the flaw mean that exploitation is plausible with standard user privileges. Because the flaw is not listed in CISA KEV, no active exploits are currently confirmed, but the high CVSS combined with the ease of delivering a vulnerable repository warns that the risk warrants immediate action.